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

JUnit test report: Age and failedSince are wrong if test method names are not unique

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • junit-plugin
    • None

      In the JUnit test report the age and failedSince values are sometimes wrong. A newly failed test sometimes gets an age greater than 1 and a failedSince pointing to a build where the test did not fail.

      I found out that this always happens to tests whose failed method names are not unique. If there are other failed tests with the same method names in the previous report, the wrong failure seems to be recognized as the predecessor.

      In my opinion this could be easily fixed by returning

      className + '.' + testName instead of just testName from CaseResult.java#getTransformedTestName

          [JENKINS-56755] JUnit test report: Age and failedSince are wrong if test method names are not unique

          Seems like a duplicate of JENKINS-30413, which has a test case and purposed fix.

          Stephen McCants added a comment - Seems like a duplicate of JENKINS-30413 , which has a test case and purposed fix.

          Lars added a comment -

          ... and is still not merged

          Lars added a comment - ... and is still not merged

          Yes, I just pinged that ticket requesting a little attention... I also voted for it since I just hit this problem myself.  Hopefully it can be fixed easily with just a little attention.

          Stephen McCants added a comment - Yes, I just pinged that ticket requesting a little attention... I also voted for it since I just hit this problem myself.  Hopefully it can be fixed easily with just a little attention.

          Lars added a comment -

          This has been fixed a while ago

          Lars added a comment - This has been fixed a while ago

            Unassigned Unassigned
            wolterhis Lars
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: