Remove ConsiderFixturesAsSpecialTests #7189
Merged
+5
−449
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Evangelink
approved these changes
Jan 12, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ConsiderFixturesAsSpecialTestsis an opt-in feature that causes test fixtures (e.g, class/assembly init/cleanup) to be discovered as fake test cases. The code related to this feature is quite big, the feature has been buggy for long, and people are unlikely to be using it. I think it's better to remove it. In future, we might want to implement it differently, in collaboration with Test Explorer so that we have a way to Test Explorer to say this test result is related to a fixture and it gets displayed in a more proper way and have a proper experience in IDE. The impact of removing the feature is low as it only affects the UX.Closes #3376
Closes #3377
Closes #5716