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

Test failures do not display useful information in drilldown

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • junit-plugin
    • None
    • Platform: All, OS: Linux

    Description

      When I click on the "Latest Test Result (4 failures / +- 0)" link on the project
      page, then down into the failing package, class and tests the only output is:

      Error Message

      "
      Stacktrace

      Standard Output

      Attachments

        Activity

          Verified in my use case. That's OK.

          gbois Gregory Boissinot added a comment - Verified in my use case. That's OK.

          adding myself as cc

          gbois Gregory Boissinot added a comment - adding myself as cc

          Code changed in hudson
          User: : abayer
          Path:
          trunk/hudson/main/core/src/main/java/hudson/tasks/junit/TestResultAction.java
          trunk/hudson/main/core/src/main/resources/hudson/tasks/junit/CaseResult/index.jelly
          trunk/hudson/main/test/pom.xml
          trunk/hudson/main/test/src/test/java/hudson/tasks/junit/CaseResultTest.java
          trunk/www/changelog.html
          http://fisheye4.cenqua.com/changelog/hudson/?cs=20835
          Log:
          [FIXED JENKINS-4257] Junit failure error messages and stacktraces should render properly in all cases now.

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : abayer Path: trunk/hudson/main/core/src/main/java/hudson/tasks/junit/TestResultAction.java trunk/hudson/main/core/src/main/resources/hudson/tasks/junit/CaseResult/index.jelly trunk/hudson/main/test/pom.xml trunk/hudson/main/test/src/test/java/hudson/tasks/junit/CaseResultTest.java trunk/www/changelog.html http://fisheye4.cenqua.com/changelog/hudson/?cs=20835 Log: [FIXED JENKINS-4257] Junit failure error messages and stacktraces should render properly in all cases now.
          abayer Andrew Bayer added a comment -

          This is caused, I believe, by the lack of a check for null testData in
          hudson.tasks.junit.TestResultAction.getActions, along with HyperlinkingOutTag
          still being used with the stacktrace output, which has already been processed in
          the same way by hudson.tasks.junit.CaseResult.annotate. I've fixed this, but am
          currently writing a test case for it.

          abayer Andrew Bayer added a comment - This is caused, I believe, by the lack of a check for null testData in hudson.tasks.junit.TestResultAction.getActions, along with HyperlinkingOutTag still being used with the stacktrace output, which has already been processed in the same way by hudson.tasks.junit.CaseResult.annotate. I've fixed this, but am currently writing a test case for it.

          People

            abayer Andrew Bayer
            agenticarus agenticarus
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: