Open
Conversation
Author
|
@microsoft-github-policy-service agree |
|
This change was originally made in 2019 |
|
It looks like this plugin is still being maintained for VS2026. Correctly displaying the status for skipped tests would greatly enhance the UX for the C++ test suites in our organization. In order to not get false negatives on tests, that are run conditionally, we are forced to use our own workarounds in main(). However, the end result of having tests grayed out with "not executed" is not all that satisfactory from a developer's POV either. Here's also a link back to the VS developer community issue: |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
I've cherry-picked the commit from the GTA project (csoltenborn#262) -- without other unrelated changes, and made minor changes to make it work in this fork.
I couldn't get a fully working setup (or did not understand how to properly run all tests), so I'd suggest to maintainers to take a look :) Otherwise, my team started used it (as a replacement of the official extension) and so far, no issues.
I'll report back if anything is raised.