-
New Feature
-
Resolution: Fixed
-
Minor
-
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.
- is duplicated by
-
JENKINS-48199 Screen for all tests should be available, showing test duration
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- is related to
-
-
- Open
-
[JENKINS-43892] Developer would like to see all successful test results
Jan
created issue -
Jan
made changes -
| Description |
Original:
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. |
New:
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. |
| Summary | Original: Add possibility to access test results including their output | New: Developer would like to see all successful test results |
| Epic Link | New: JENKINS-43952 [ 181484 ] |
Jan
added a comment - Hi James, thanks for your feedback. I'm afraid that providing especially the log output as CSV is not appropriate since tests might produce plenty of Information. What do you think?
Jan
added a comment - Hi James, thanks for your feedback. I'm afraid that providing especially the log output as CSV is not appropriate since tests might produce plenty of Information. What do you think? janr is the log output for successful tests relevant to your use case?
Jan
added a comment - Hi James. Yes, it is very important for me and my clients because most often it reflects some kind of protocol to which the customer has access. I saw that you changed the title of this issue, unfortunately this isn't reflected in the title anymore.
Jan
added a comment - Hi James. Yes, it is very important for me and my clients because most often it reflects some kind of protocol to which the customer has access. I saw that you changed the title of this issue, unfortunately this isn't reflected in the title anymore. 
Craig Rodrigues
added a comment - 
on this request. While I understand that the BlueOcean UI is quite different from the classic UI,
it is important to display the results of tests and a finer granularity than: "TESTS PASS" or "TESTS FAIL".
I use the JUnit plugin quite heavily to publish the results of JUnit style tests.
If there was a way to plug in the output of the JUnit plugin (and other similar plugins which publish test results) into the Blue Ocean UI, that would be really nice.
Even if there was a link from the Blue Ocean UI
to the classic UI's JUnit plugin test results, that would be a step in the right direction.
Craig Rodrigues
added a comment -
on this request. While I understand that the BlueOcean UI is quite different from the classic UI,
it is important to display the results of tests and a finer granularity than: "TESTS PASS" or "TESTS FAIL".
I use the JUnit plugin quite heavily to publish the results of JUnit style tests.
If there was a way to plug in the output of the JUnit plugin (and other similar plugins which publish test results) into the Blue Ocean UI, that would be really nice.
Even if there was a link from the Blue Ocean UI
to the classic UI's JUnit plugin test results, that would be a step in the right direction. 
Brett Higgins
added a comment - Don't you already have this problem for failing tests as well? What if a build generates a Junit test result with hundreds of thousands of failing tests? How will Blue Ocean handle it?
If the current answer is that the page becomes sluggish or otherwise fails to deliver the list of results, I could see the case for not doing this for successful test results, since the scenario I described is much less common than having a huge number of passing tests. However, if the current answer is more along the lines of "we cap the number of results returned to a fixed amount," it seems doable to apply the same policy to successful test results. If the cap is fairly high, maybe most projects would be able to see their successful test result details, and the x% at the top with hundreds of thousands of tests would at least not have their browser hang (or whatever other negative experience).
Brett Higgins
added a comment - Don't you already have this problem for failing tests as well? What if a build generates a Junit test result with hundreds of thousands of failing tests? How will Blue Ocean handle it?
If the current answer is that the page becomes sluggish or otherwise fails to deliver the list of results, I could see the case for not doing this for successful test results, since the scenario I described is much less common than having a huge number of passing tests. However, if the current answer is more along the lines of "we cap the number of results returned to a fixed amount," it seems doable to apply the same policy to successful test results. If the cap is fairly high, maybe most projects would be able to see their successful test result details, and the x% at the top with hundreds of thousands of tests would at least not have their browser hang (or whatever other negative experience). 
janr thanks for filing this feature request.
Unfortunately there is not an easy fix without a redesign. Blue Ocean has to cope with Pipelines range from having a few tests to hundreds of thousands of tests which means cannot display all successful tests and have it work for all users.
We could also look at alternative ways to get you this data. For example, if your client is looking for proof of tests we could allow you to export the tests to a Excel or CSV file rather than displaying every test on this screen.
What do you think?