VSTestBridge: Handle TestPropertyAttributes.Trait instead of special casing specific properties #5644
+26
−28
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.
Fixes #5642
Instead of special casing
MSTestDiscoverer.TestCategory
andTestObject.Traits
, we instead useTestPropertyAttributes.Trait
to determine whether a property is a trait.When the property value is
string[]
, we assume it's the "categories". Otherwise, we expect it to beKVP<string, string>[]
which is a list of traits as key value pairs.NOTE: NUnit needs this. See nunit/nunit3-vs-adapter#1258