Using TFS 2012, we have a build configured to run our NUnit tests. All our test projects have a NUnit Test Adapter for VS2012 and VS2013 the nuget package is installed. With the corresponding extension installed, all tests are performed locally in VS2013 using the test harness (Test Explorer window).
However, our tests are performed on our TFS build server, but the test results in our build produce an incorrect test counter. Using only one of our test projects, which has 228 unit tests, assembly reports of 65 out of 65 were executed correctly. When viewing the results of the 65 tests that appear, these are the first 65 tests sorted by the full class name in alphabetical order. However, when we look at the build log, we see that all 228 unit tests were successfully completed.
What would a wrong test counter do? And any ideas on how to fix this?
source
share