JUnit reports with similar content is too complicated to read

Problem to solve

Currently, each job gets its own report in the merge request widget. However, if the failures are same in multiple jobs for the same test the results are messy and hard to read.

Intended users

• Sasha (Software Developer) - who wants to know why a single change created multiple jobs to fail.

User experience goal

The user should be able to use the Test Summary Widget to understand how many different tests failed in addition to how many jobs failed.

Proposal

The UI should collect failures that occur in the same file but multiple jobs and display them once ("failures are same" = same error message + same line caused the error).

This issue will need some UX support from the GitLab team or a community contribution before it can move forward to development.

Further details

Use case: Running same set of tests in multiple configurations (eg: different OSs, different Ruby versions, different architecture)

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references