TeamCity Reporter. Remove flow id from name of test suites.#3054
TeamCity Reporter. Remove flow id from name of test suites.#3054bradwilson merged 2 commits intoxunit:v2from
Conversation
|
@dotnet-policy-service agree |
|
This was done purposefully. Collection names are not required to be globally unique, so in order to differentiate test collections from one assembly from test collections with the same names in another assembly, the collection unique ID must be part of the name. In addition, although you're trying to "unbreak" your own history, this change would break history for other people. |
No, I'm not trying to break my history, it's already broken after the xunit.runner.visualstudio update, which was not immediately noticed. |
|
Can you prove a repro project that illustrates this? |
|
Here is an example of running a few tests in a test project: After a clean & rebuild, I get the exact same values for the flow IDs and collection unique ID. |
|
Never mind, the ID stability is in the v3 tree, not the v2 tree. Sorry for the confusion. |
|
Anything empty test |
Don't think anything negative, but this seems like overengineering to me. The test collection name consists of namespace and class name, making different solutions with the same namespace is like shooting oneself in the foot. |
Collection names are user customizable. |
|
There are tests that need to be updated. See the build failure: https://github.com/xunit/xunit/actions/runs/11725900453/job/32676586129?pr=3054 |
Sorry about that, didn't immediately understand how to build and run testing locally. Anyway, in the local launch I couldn't get a full test pass because of the different locale from the English one. Hopefully now they will pass pepeline :) |
|
Once the CI build is complete, this will be available in |
Request fixes this issue xunit/visualstudio.xunit#394
The output name of the test suites does not need a flow id.
I can assume that during the development of xunit.runner.visualstudio 2.5 version, flow id generation for test suites was fixed, which caused test suites to stop being constant, which breaks the history of test execution on Teamcity.