Tests that changed most by execution time in Test Summary Widget
Problem to solve
As a developer, I want to know which n tests slowed down the most between my branch and the target branch, so I can ensure we aren't slowing down builds/deployments down stream and everyone's future work.
Intended users
- Sasha (Software Developer) - who wants to know if their change has slowed any tests down a lot so they can review, fix and keep pipelines speedy.
User experience goal
the user should be able to use the UI (existing Test Summary Widget) to see which n tests slowed down the most / beyond a threshold between the latest execution in the MR pipeline and the last known execution in the target branch.
Proposal
- Add an area to display tests that slowed down the most
- Show n tests
- parsing every JUnit.xml report file twice is going to be slow, maybe this feature is on demand or loads in the background?
Further details
This idea was brought up by the Plan team who already is using rspec profiling to build views similar to this outside of the product.
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
Edited by James Heimbuck