![]() No code coverage results are created, and the output window says the following: However, I'm running into an issue when trying to analyze code coverage for all of the tests. Unit tests will be run on check-in, integration tests nightly. The number of tests, combined with re-setting the infrastructure dependencies between tests, has resulting in a rather lengthy test run for the full suite (around 45 minutes at the moment). But I'm also including a lot of integration tests which have more external infrastructure dependencies. For the most part, running the unit tests is no big deal. I'm working on a pretty sizable suite of tests for some code I'm writing (in Visual Studio 2012).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |