Developers lack fine-grained control when debugging failing tests
Developers want to preview, filter, rerun, reorder, and repeat tests without paying the time cost of full-suite runs. When failures are intermittent or happen in CI, reproducing and diagnosing them can also mean digging through logs and artifacts or rebuilding a CI-specific environment. Existing workarounds in the reports include looping tests, renaming files to change order, and manually inspecting CI artifacts.
For software developers and test engineers. Mentioned from Jun 2014 to Aug 2026 on GitHub and Hacker News.
13 different people described this problem in 11 separate discussions.
- Indie fit
- 6.0/10
- Pain
- 6.5/10
- Frequency
- 9.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 4.7/10
- Who pays
- Businesses
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Running them takes 10 minutes and 3 tests fail. - For the next several minutes I'll focus on these 3 tests, changing code and rerunning them many times. - While I do this, I want the Test Runner UI to only watch/rerun these 3 tests, until they pass
Allow to rerun only failed tests directly from the Test Runner UI > @jennifer-shehane and @Superkunair you both refer to issues and solutions to handle flaky tests by rerunning them. That's not what I'm looking for. I'm looking for a feature in the Test Runner UI.
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 5 places to find your first customers
- 11 more quotes from people who have this problem
- Current workarounds, existing solutions and risks