Link to file from test summary for failed tests

Problem to solve

When a user is reviewing an MR they see a helpful view of tests that ran in the MRs pipeline that have a different result from the target branch. In that view you also get a helpful view of the trace of the error BUT not so helpful is no way to go view the code of the failure.

As a user reviewing test summary in an MR, I want to be able to navigate to a file and line of a test that failed, so that I can quickly fix broken tests to get a green pipeline.

Intended users

• Sasha (Software Developer) - who is reviewing their MR or the MR of another developer and wants to see the test code.
• Simone (Software Engineer in Test) - who is looking at updating a failed test when reviewing the MR.

-->

User experience goal

The user should be able to go from a test failure notice in the Test Summary widget to the file that contains that test in the Repository -> Files view with a single click to review the failing test code.

Proposal

Add to the interface the file name and a way to navigate to the file of the failed test.

Further details

This came up original in discussion of the GitLab quality team using the filename of a failed test in issues.

Today the following is displayed on the Test Summary

A Job and Classname is shown that had the test failure but not the file the test was in

The metadata has a great stack trace but no way to go see the failing test

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

changed milestone to %Backlog

added Category:Code Testing and Coverage devopsverify featureenhancement grouppipeline security typefeature labels

mentioned in issue #119032 (closed)

@mlapierre - I'd appreciate your and @zeffmorgan giving the use case described here a sanity check for me to ensure I captured your workflow correctly and how this might help. Thanks!

@jheimbuck_gl That sounds good to me!

You may also want to ask some frontend and backend engineers, as they're more likely to use the test summary in the MR widget (the end-to-end (QA) test results don't appear in the MR widget yet).

added internal customer label

added UX label

removed typefeature label

added [deprecated] Accepting merge requests label

added sectionops label

added typefeature label

removed featureenhancement label

This is a duplicate of work (#22336 (closed)) scheduled for %13.11

marked this issue as a duplicate of #22336 (closed)

closed

marked this issue as related to #22336 (closed)