Mostly, we see issues in ClassIntialize and TestInitialize, or in the TestMethod itself. In my opinion, the fastest and easiest way is to have the tests log to a rolling tail log file that is updated during the different parts of the test.So we need some way to track what test is having problems and where is it having an issue. The test can be "breaking" due to issues in many places including TestInitialize, ClassInitialize, etc. The first thing that needs to be done is to find the test that is causing the issue. Sometimes, the failing test has to be run on the build server with just the right settings to reproduce the issue. Below, I will refer to tests " breaking", this means the test is causing an exception that is breaking the test executioner and is different from a test just failing. We have found this issue happening when using mstestor in XAML builds and VNext Builds. Most of the time, we have not been able to reproduce this in a development environment, but consistently in the build environment tests are breaking the test runner. The issue comes from tests that are breaking the Test Execution system. Many times, we have run thousands of tests just to find only a few hundred actually finish, or several hundred were missing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |