Pipeline test page does not include test report from child pipeline

Release notes

When a pipeline has child pipelines, we show the children in the pipeline graph, but we do not include tests from the child pipelines. Since our Test Summary MR widget aggregates the data from child pipelines in the summary, we will include test jobs in the Tests tab. This way, if you were to view the full report of the Test Summary widget, you would see all tests that were aggregated into the summary.

Problem to solve

The pipeline test report page currently does not include test reports from child pipelines. Example: https://gitlab.com/gitlab-org/gitlab/-/pipelines/543961603/test_report

We will be including reports from child pipelines into Merge Request, which means the experience of the full report vs the MR widget summary will be different, since the Tests list does not include tests from child pipelines.

We also show the child pipelines in the pipeline graph, but don't include child pipeline tests or jobs when viewing the parent pipeline. The experience is inconsistent and leaves out crucial information for the developer.

Intended users

• Sasha (Software Developer)

User experience goal

The user should be able to see child pipeline tests when a parent pipeline includes them.

Proposal

• Add child badge underneath test job's name
• Add child pipeline ID as a link (gray-900) next to child badge

🎨 See designs in design management

🖌️ Design specs in Figma

Further details

Permissions and Security

Documentation

Availability & Testing

Available Tier

Feature Usage Metrics

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

What is the type of buyer?

Is this a cross-stage feature?

What is the competitive advantage or differentiation for this feature?

Links / references

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.