Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Incorrect test result view in Azure DevOps after upgrading MSTest to 2.2.4 and higher
See original GitHub issueDescription
After I updated MSTest.Framework and MSTest.Adapter to 2.2.4 and higher, the test results in Azure DevOps are displayed incorrectly. Each test interation is displayed in a new line. Before that, the interations were shown under a test case.
For example: A Test with 2 iterations
Before: TestCase12
- Iteration1
- Iteration2
Currently
- TestCase12
- TestCase12
This a screenshot for the test results on Azure DevOps
For example: Test Case 1129
TRX-File look like different
After the upgrade, the trx file does not contain an <InnerResults> element
Hier is a screenshot fom trx-file
I use VS 2019 16.11.6 I’m not sure if this is a bug or a new configuration. This is my test configuration: Configure unit tests by using a .runsettings file
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:69 (23 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Duly noted. Believe me, I am not happy about this either. We are looking into conditionally reverting this change until it is fixed in azdo.
This is not a bug, mstest now reports data driven tests as single tests. This was done to bring parity to how xunit and nunit does it.
@Haplois There are few duplicates of this issue. Could you link them all to a single one, and post an update on when the work on AzDO will be finished, please?
Also correct my statement above if I am wrong 😃