whenresets.cc

AI usage limit reset times and history

English
Back to prompt library

Find the test gaps that actually matter

You don't know where tests matter most and just stare at the coverage number.

When to use it Before you start writing tests

30 minUsage: MediumCodebaseRead-only

What you get

A risk-ranked test plan you can implement right away.

Before you start

  • The repo has tests or clearly identifiable critical paths

Steps

  1. Review recent changes and critical business paths
  2. List failures users would notice
  3. Confirm what the existing tests actually prove
  4. Specify setup, assertions and target files

Deliverables

  • Risk map
  • Test case list

Done when

  • Each suggestion includes a failure mode and an assertion
  • Low-value tests that only pad coverage are left out

Paste this into your agent

Do a read-only test gap review. Look at recent changes, critical paths, error handling and edge cases. Explain what the existing tests actually prove, and list missing tests by risk; for each, give the failure mode, setup, assertions and where it should live. Do not edit any files. Stop once you've produced the above; don't go on to anything else.