Test summary should explain if junit tests are expired
Release notes
Our test summary includes a list of all junit tests, whether they are expired or not. That means that clicking on one could lead to an empty page. We should improve this experience by indicating this is expired before even clicking on it.
Problem to solve
Users may come to an old test summary and see that junit tests are listed, try to get more information, and see that each is expired and have no data populating their detail summaries. This is probably annoying / confusing as they have to take an extra step just to see they don't have data.
Intended users
Metrics
User experience goal
Indicate that a junit test is expired/useless so the dev doesn't have to waste their time searching through an expired report.
Proposal
Check if test cases in a test suite are expired.
- If all are expired, add an expired badge to the test suite.
- If only some are expired, do not add a badge. We will show an empty state for the individual cases that are expired based on #296963 (closed)
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
What does success look like, and how can we measure that?
As a developer, when I come to an old test summary report, I can easily indicate if the data is expired or no longer useful for me. We can measure that by seeing less clicks on junit reports for an old pipeline / expired junit tests.
What is the type of buyer?
Is this a cross-stage 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.