Use utility classes in test report
What does this MR do and why?
Refactor the full unit test report (the Tests
tab on the pipeline page) to use gitlab-ui utility classes.
Screenshots or screen recordings
There should be only negligible visual differences - the statistics above the progress bar are slightly more evenly spaced, for example
before | after | |
---|---|---|
summary view | ||
suite view |
How to set up and validate locally
git checkout master
- find/clone a project that generates test reports
- run a pipeline in the project, wait for it to finish so that the test report artifacts are available
- navigate to the pipeline page =>
Tests
tab - observe the test summary table, click into a suite, observe the list of tests, try different window widths, etc.
git checkout 230996-use-utility-classes-in-test-report
- the test summary table and list of tests in the suite should look almost identical
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #230996 (closed)
Edited by Miranda Fluharty