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

Developer would like to see all successful test results

    • Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Minor Minor
    • blueocean-plugin
    • None
    • Jenkins ver. 2.46.2 (Docker-based)
    • Blue Ocean 1.5 - beta 2

      In many cases people want to see the full set of tests, including all passing tests. 

      Scope

      • Add a new paginatable section for "Passed" tests. Section should be below all other test sections.
      • Functional and unit tests to cover passed tests section.

      Original request
      In the classic version of Jenkins we grant access to our customers the test output. It's supposed to be some kind of proof that we implemented their feature requests. Furthermore, this is a possibility for them to verify that requested behaviour works as expected/specified in the requirements. In the classic verison one can always access published test results and also enter the output being produced in the tests. In blue ocean I only get a message that all tests succeeded when entering the "Test" tab (see attached screenshot).

      It would give value if one could access the tests and also enter the test output in any case. If it would be an Extension point one could provide their own implementation.

          [JENKINS-43892] Developer would like to see all successful test results

          James Dumay added a comment -

          ccaraivan we plan on adding a "Trends" tab to the Pipeline so that you can see duration trends for all sorts of things. Perhaps this is where we could show if your tests are taking longer to run etc?

          James Dumay added a comment - ccaraivan we plan on adding a "Trends" tab to the Pipeline so that you can see duration trends for all sorts of things. Perhaps this is where we could show if your tests are taking longer to run etc?

          James Dumay added a comment -

          brettdh what timing information do you specifically need?

          James Dumay added a comment - brettdh what timing information do you specifically need?

          jamesdumay That could help, but they would need to have a break down/drill down. For example for Java we would need to be able to see timings/trends at package level and test level. If Jenkins core can't provide them at least there should be hooks for individual plugins to add stuff there, for example for Junit categories and such.

          Costin Caraivan added a comment - jamesdumay That could help, but they would need to have a break down/drill down. For example for Java we would need to be able to see timings/trends at package level and test level. If Jenkins core can't provide them at least there should be hooks for individual plugins to add stuff there, for example for Junit categories and such.

          Brett Higgins added a comment -

          jamesdumay The same timing information that's available in test results outside Blue Ocean: the execution time of each test, as reported in the JUnit XML file. Blue Ocean currently reports this for failing tests, but not for passing tests (since it reports nothing for passing tests).

          Brett Higgins added a comment - jamesdumay The same timing information that's available in test results outside Blue Ocean: the execution time of each test, as reported in the JUnit XML file. Blue Ocean currently reports this for failing tests, but not for passing tests (since it reports nothing for passing tests).

          James Dumay added a comment -

          Successful test display is shipping in the next release.

          James Dumay added a comment - Successful test display is shipping in the next release.

          jamesdumay Cool! Somewhat related to this - to not slow down page loading, does this only load a partial list at first, with the possibility to load the full list, if wanted? We have thousands of tests.

          Costin Caraivan added a comment - jamesdumay Cool! Somewhat related to this - to not slow down page loading, does this only load a partial list at first, with the possibility to load the full list, if wanted? We have thousands of tests.

          This looks cool - In order to see this - is this coming from a junit generated file?

          Paul Dragoonis added a comment - This looks cool - In order to see this - is this coming from a junit generated file?

          Craig Rodrigues added a comment - - edited

          michaelneale jamesdumay undera

          I am a heavy user of the Performance Plugin https://wiki.jenkins.io/display/JENKINS/Performance+Plugin

           

          Right now, the Performance Plugin creates a new link for each job such as:

          [https://jenkinshost/job/jobName/247/performance/

          T|https://jenkinshost/job/jobName/performance/]here are screenshots of what the Performance Plugin produces here: https://wiki.jenkins.io/display/JENKINS/Performance+Plugin?focusedCommentId=135470852#comment-135470852

           

          At this link there are graphs and tables listed which display the performance results.

          Is it possible to view the test results of the Performance Plugin in the BlueOcean UI?

           

          This would be extremely useful.

          Craig Rodrigues added a comment - - edited michaelneale jamesdumay undera I am a heavy user of the Performance Plugin https://wiki.jenkins.io/display/JENKINS/Performance+Plugin   Right now, the Performance Plugin creates a new link for each job such as: [https://jenkinshost/job/jobName/247/performance/ T|https://jenkinshost/job/jobName/performance/]here are screenshots of what the Performance Plugin produces here:  https://wiki.jenkins.io/display/JENKINS/Performance+Plugin?focusedCommentId=135470852#comment-135470852   At this link there are graphs and tables listed which display the performance results. Is it possible to view the test results of the Performance Plugin in the BlueOcean UI?   This would be extremely useful.

          Michael Neale added a comment -

          dragoonis yes - any junit/xunit type xml report file that is archived by the test archiver (usually a step like: junit 'path/to/stuff') will work with this. 

          hey rodrigc interesting. That is worthy of a fresh ticket. Perhaps you could team up with imeredith who was looking at ways to add data driven extension points so that other plugins could add links to the performance report pages. Would it be enough that the results screen (somewhere...) has links to /performance to start with? (ie no new screens, just links?)

           

           

          Michael Neale added a comment - dragoonis yes - any junit/xunit type xml report file that is archived by the test archiver (usually a step like: junit 'path/to/stuff') will work with this.  hey rodrigc interesting. That is worthy of a fresh ticket. Perhaps you could team up with imeredith who was looking at ways to add data driven extension points so that other plugins could add links to the performance report pages. Would it be enough that the results screen (somewhere...) has links to /performance to start with? (ie no new screens, just links?)    

          Craig Rodrigues added a comment - michaelneale I filed JENKINS-50589

            imeredith Ivan Meredith
            janr Jan
            Votes:
            4 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: