Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-61766

JUnit report misses test cases from duplicate testsuites

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: junit-plugin
    • Environment:
      Jenkins ver. 2.204.6
      JUnit Plugin (junit): 1.28
      OS: Ubuntu Linux 18.04
    • Similar Issues:

      Description

      When the same testsuite appears in multiple files with the same timestamp, only the first testsuite is evaluated, any testcases in following files are silently ignored.

       

      I attached two test report XML files with typical output of our build runs, yet simplified as much as possible. As you can see, both files contain a different test case of the same testsuite "TestFoo". If the test execution is very fast it can happen that both the testsuites have the same timestamp, in which case every testcase but the first is not included in the report, as you can see on the attached screenshot.

       

      The expected behaviour is, that all the testcases are included in the report and the stage fails if any of the testcases failed.

       

      I consider this a major bug as it allows failed tests to be ignored and in the consequence broken software can be reported as "successfull" when it isn't.

       

        Attachments

        1. JUnit Report.png
          JUnit Report.png
          7 kB
        2. test_1.xml
          0.4 kB
        3. test_2.xml
          0.4 kB

          Activity

          Hide
          timja Tim Jacomb added a comment -

          I think this is fixed in the latest release, resolving please re-open if not fixed.

          Show
          timja Tim Jacomb added a comment - I think this is fixed in the latest release, resolving please re-open if not fixed.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            exomo Kai Bublitz
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: