We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xunit
TestResult.Traits
TestResult.TestCase.Traits
nunit
TestResult.Properties
TestResultInfo.Traits should encapsulate the test framework specific nuances.
TestResultInfo.Traits
See spekt/xunit.testlogger#33 for the workaround used in xunit.testlogger. The fix should remove this workaround.
xunit.testlogger
The text was updated successfully, but these errors were encountered:
We're using TestCase.Traits in TestResultInfo. Also exposed TestResultInfo.Properties as optionally filled by specific adapters (NUnit only for now).
TestResultInfo
TestResultInfo.Properties
Sorry, something went wrong.
codito
No branches or pull requests
xunit
does not fill inTestResult.Traits
, instead it updatesTestResult.TestCase.Traits
. See No traits when updating to 3.0.56 xunit.testlogger#32nunit
does fill inTestResult.Traits
but it provided additional elements inTestResult.Properties
. See https://github.com/spekt/nunit.testlogger/blob/master/src/NUnit.Xml.TestLogger/NUnitXmlSerializer.cs#L281TestResultInfo.Traits
should encapsulate the test framework specific nuances.See spekt/xunit.testlogger#33 for the workaround used in
xunit.testlogger
. The fix should remove this workaround.The text was updated successfully, but these errors were encountered: