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
This block of code needs to handle the skipped case and emit a skipped element. Currently anything not Failed is considered successful.
skipped
Failed
JUnitTestLogger/src/JunitTestLogger/JUnitXmlTestLogger.cs
Lines 370 to 387 in 25ae7b4
some speculative code that might fix this:
if (result.Outcome == TestOutcome.Skipped) { var skipped = new XElement("skipped"); element.Add(skipped); }
The text was updated successfully, but these errors were encountered:
closest i could find to a spec for junit output for a test case:
https://github.com/behave/behave/blob/85bca4533ae4fb0cb27b65d04c5dd50355210395/etc/junit.xml/junit-4.xsd#L38-L53
<xs:element name="testcase"> <xs:complexType> <xs:sequence> <xs:element ref="skipped" minOccurs="0" maxOccurs="1"/> <xs:element ref="error" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="failure" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="system-out" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="system-err" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="name" type="xs:string" use="required"/> <xs:attribute name="assertions" type="xs:string" use="optional"/> <xs:attribute name="time" type="xs:string" use="optional"/> <xs:attribute name="classname" type="xs:string" use="optional"/> <xs:attribute name="status" type="xs:string" use="optional"/> </xs:complexType> </xs:element>
Sorry, something went wrong.
if anyone else comes across this issue, take a look at this alternative spekt/junit.testlogger#12
No branches or pull requests
This block of code needs to handle the skipped case and emit a
skipped
element. Currently anything notFailed
is considered successful.JUnitTestLogger/src/JunitTestLogger/JUnitXmlTestLogger.cs
Lines 370 to 387 in 25ae7b4
some speculative code that might fix this:
The text was updated successfully, but these errors were encountered: