Currently, the Tests page displays results across all runs without scoping options, which means the same test appears multiple times, large suites span hundreds of pages, and failure rates reflect older historical data even after fixes are applied. Customers have expressed that having controls to surface the most relevant and up-to-date results would significantly improve their ability to act on test health insights.

Suggested Feature:

Introducing filtering, grouping, and stats controls on the Tests page would give customers the ability to focus on what matters most:

• Allow customers to scope the Tests page to the most recent run on main/master, reducing duplicate entries and making sort views like "slowest tests" more actionable.
• Collapse individual test cases under their parent suite, making large test suites easier to navigate and reducing pagination.
• Allow customers to define the time period or run count used to calculate failure rate and flakiness, so that stats reflect current test health rather than historical data.
• Apply recency weighting to failure rates so that recently fixed tests are reflected accurately without waiting for old data to age out.