Uploaded image for project: 'Maven Surefire'
  1. Maven Surefire
  2. SUREFIRE-1533

surefire-test-report.xsd has too narrow a definition for testcase time attribute

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: JUnit 5.x support
    • Labels:
      None

      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

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              tsondergaard Thomas Sondergaard
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: