[SUREFIRE-1533] surefire-test-report.xsd has too narrow a definition for testcase time attribute

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.1.2
• Component/s: JUnit 5.x support
• Assignee: Michael Osipov
• Reporter: Thomas Sondergaard
• Created: 05/Jul/18 13:18
• Updated: 29/May/23 19:35
• Resolved: 29/May/23 19:26

Description

The jenkins xunit plugin uses the surefire jenkins schema for validation.

http://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report.xsd

Many test tools, also outside the Java world, use the junit format, but it has (apparently) not been well-specified so a number of tools generate junit reports that do not match the xsd above. Specifically I have run into the problem that the time attribute is much too narrowly defined in the schema. It does not allow specifying time with sub-millisecond precision or use of scientific notation for the time.

Are there any reason not to allow any floating point number for the (testcase) time attribute?

If you do not want to allow scientific notation at least allow more than three decimals.

See also https://issues.jenkins-ci.org/browse/JENKINS-52152

Issue Links

• is fixed by: SUREFIRE-2175 Turn time attribute to xs:float in Surefire test report schema
• requires: SUREFIRE-2164 Simplify serialization of elapsed time in StatelessXmlReporter
• requires: SUREFIRE-2167 Simplify deserialization of elapsed time in TestSuiteXmlParser