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

["Michael Osipov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SUREFIRE-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov reassigned SUREFIRE-1533:
----------------------------------------

    Assignee: Michael Osipov

> surefire-test-report.xsd has too narrow a definition for testcase time attribute
> --------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-1533
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1533
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: JUnit 5.x support
>            Reporter: Thomas Sondergaard
>            Assignee: Michael Osipov
>            Priority: Major
>
> 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



--
This message was sent by Atlassian Jira
(v8.20.10#820010)