You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For context, we are using this adapter outside of the visual studio IDE as part of a command line tool that discovers tests in a Visual Studio project. It would be a real advantage during discovery to be able to see the skip reason for any tests. The SkipReason is available during discovery for the ITestDiscovered object but is lost after the creation of the TestCase.
During creation of the TestCase object it appears some ITestDiscovered values are provided as properties of the TestCase object (TestCaseUniqueID, Explicit). It would make sense to also provide the SkipReason as another property.
It appears that any change would not negatively affect the existing adapter, and it would result in not losing the original SkipReason in the TestCase.
The text was updated successfully, but these errors were encountered:
One thing that needs clarification: v3 supports unconditionally skipped tests and conditionally skipped tests. The difference is that both set Skip="...", but conditionally skipped tests also set either SkipWhen="..." or SkipUnless="...", and whether or not to skip is a decision that's made at runtime.
I'm assuming, based on your description, that you would only want us to set a SkipReason when the tests are unconditionally skipped, correct?
For context, we are using this adapter outside of the visual studio IDE as part of a command line tool that discovers tests in a Visual Studio project. It would be a real advantage during discovery to be able to see the skip reason for any tests. The SkipReason is available during discovery for the ITestDiscovered object but is lost after the creation of the TestCase.
During creation of the TestCase object it appears some ITestDiscovered values are provided as properties of the TestCase object (TestCaseUniqueID, Explicit). It would make sense to also provide the SkipReason as another property.
It appears that any change would not negatively affect the existing adapter, and it would result in not losing the original SkipReason in the TestCase.
The text was updated successfully, but these errors were encountered: