Unit Test report view UX cleanup
Release notes
Problem to solve
As a gitlab user looking at the unit test report, I want a clean view of data from failed tests (test file name, trace, test duration, etc.), so that I can make decisions / issues quickly and efficiently to get this pipeline passing.
Intended users
- Sasha (Software Developer) - who is looking at the tests that failed in their current MR on the pipeline page because they don't use MRs.
- Simone (Software Engineer in Test) - who is reviewing failed tests from scheduled builds / an MR from a developer.
User experience goal
The user should be able to easily view, select, and share information about failed tests within the gitlab ui.
Proposal
One option would be to re-use the existing modal from the Test Summary to display some of this data including the trace. That modal is displayed below. It would need to be augmented with Test History and Filename.
The column name should be renamed from Trace to Details and the column contain a link/button (@v_mishra to help decide) to open the modal.
Further details
Several new features are being or have been introduced to add functionality to the Unit Test report since it's introduction. This has improved the feature set but decreased the usability of the features unfortunately as the page gets more crowded with information. This only gets worse with filename and test history columns being added in addition to sorting the failed tests to the top so trace data is immediately presented.
Cleaning up this view so a user can still see the failed tests first but having the data from those tests more easily readable is the ideal outcome for this issue.
No matter the approach the CSS fix implemented to cleanup the scrolling should be removed/un-cleaned up/?
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
Acceptance Criteria
- Given that a pipeline outputs one or more JUnit reports, when one or more of those contains one more ore test failures, then a user on the unit test report page should be able to quickly identify and review information about failed tests (test file location, trace, history, suite and test name, etc.) in a user friendly manner.
Success metrics
- We expect that once measurement of page views of the unit test report is in place that measure will increase by 20% within 60 days after launch of the feature on gitlab.com
What is the type of buyer?
This is for the individual developer and part of the Core product.
Is this a cross-stage feature?
No.