Specify VSTestCase.FullyQualifiedName as dot-separated Boost.Test path name #104
Conversation
This file contains 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
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.
As noted by @jsutes in issue #79, Visual Studio seems to use a (undocumented?) protocol to create a hierarchy based on the FullyQualifiedName property of Visual Studio Test Case. This solution changes the slash-separated ('/') Boost.Test test paths to dot-separated ('.') names.
Note that this may cause a breaking change - users of
vstest.consolewill need to outline tests in the/Tests:command line option using the new scheme. In addition, no guarantees can be made with regards to correct visualisation of Boost.Test test cases which are manually registered via a user-specified (string) name (which may contain dots).