Artifact-based view for Junit XML
Problem to solve
This issue tackles a sub-scope of &1875 and it focuses on the problem of users not being able to find out about the full scope of their tests per pipeline making it hard to look back at test runs to fix failed ones, know if it is required to do so and having to dig through console logs to do this which is time consuming. Additionally, any current test functionality relies on merge requests being used, making it very hard to surface this information if working from just a branch.
For Developers or DevOps Engineers: When tests in my CI fail, I want a view of the aggregate test results that I can drill into, so that I can save time finding and fixing errors.
This item moves us forward in our Maturity Plan for Code Quality by moving the CI Views epic forward.
This issue will focus on the scope of:
An artifact-based view to see the amount of tests vs failed for pipeline pages. This will gather cross job test information and collectively shows it, including metadata.
Preferably this view will be flexible and thus usable beyond just Junit. It is, however, acceptable for an MVC to start off with a single format if need be.
Test suite list view
Test suite detail view (detailing the individual tests)
- Total jobs
- Total failures
- Total error rate
- Success rate
- Visual progress bar indicating total/failed
- Total time
Test suites table:
- Suite name
- Class name
- Test name
You'll be able to click a test suite row to inspect it similar to this example. This way you'll be able to dive into a test suite to all the individual tests in there. If tests are failed they will be sorted on top automatically and will show a track trace.
If possible I'd like to reinforce the back button navigation paradigm with a small animation. When the user clicks the row and we dive into a test suite, the content shifts left. Upon navigating back it will shift back right again.
Can you let me know if this is feasible?
Permissions and Security
What does success look like, and how can we measure that?
- We will track page views on the test suite detail view to determine the usage of this feature.