I am currently working on a legacy project that has around 2000 unit tests, some of which are poorly written and have unintended dependencies on other unit tests.
Some tests make use of static variables that aren't cleared between each test, some even update data in a DB and don't reseed between each test.
This means that when running the tests, sometimes individual tests fail, but then if they are run individually when debugging, they pass. How frustrating.
I am trying to find a way to determine the state of the test environment when the tests fail so that I can identify the inter dependencies and remove them if present.
To that end, is there a way using Visual Studio 2017 and MSTest, to output the actual execution order of a test run?
Aucun commentaire:
Enregistrer un commentaire