Skip to content
Log in

Test Suite Triage

Finds the tests that cost more than they catch, and fixes the flakiness that teaches everyone to ignore a red build.

0

Share this prompt

Free — no card needed

Create a free account

to open Test Suite Triage — and the other 364 prompts across 21 categories.

We store your email address to send these. We never sell it or pass it to advertisers. Withdraw at any time. Privacy Policy.

Already have an account?

CategoryCodingForDevelopersTested onClaudeChatGPT

Running it, start to finish

  1. Quarantine every flaky test out of the blocking path with a date.
  2. Work out what kind of test would have caught each escaped bug.
  3. Add integration coverage at the seams before adding more unit tests.

What you get back

The output this produces, every time.

  • Treats flakiness as the first problem, since it destroys trust in every other test.
  • Identifies tests asserting implementation rather than behaviour, which break on every refactor.
  • Checks escaped bugs against the suite's shape, which usually reveals an integration gap.

Getting better results

Where this usually goes wrong, and how to avoid it.

  • Quarantine flakes today. With a fix-or-delete date. Leaving them blocking teaches the team that red does not mean stop.
  • Delete tests that catch nothing. A slow duplicate with no meaningful assertion is a liability. Removing it makes the suite better, not worse.
  • Read the escaped bugs carefully. They usually point at the seams between components, which is where unit tests structurally cannot look.

More Coding prompts

All Coding →

Written for The AI University. Every prompt in this library is original work — authored, tested and revised here, not collected from elsewhere. 365 of them, free with an account.