Skip to content

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 Screen_Shot_2022-07-19_at_13.18.17 Screen_Shot_2022-07-19_at_13.16.20
suite view Screen_Shot_2022-07-19_at_13.18.40 Screen_Shot_2022-07-19_at_13.16.16

How to set up and validate locally

  1. git checkout master
  2. find/clone a project that generates test reports
  3. run a pipeline in the project, wait for it to finish so that the test report artifacts are available
  4. navigate to the pipeline page => Tests tab
  5. observe the test summary table, click into a suite, observe the list of tests, try different window widths, etc.
  6. git checkout 230996-use-utility-classes-in-test-report
  7. 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.

Related to #230996 (closed)

Edited by Miranda Fluharty

Merge request reports