Loading…
Loading…
Coverage percentages are easy to raise and easy to fake. What is hard is knowing which tests would actually catch tomorrow's bug, which ones assert the implementation rather than the behaviour, and which ones exist only to make the number go up. The prompts below are written for that judgement. They ask for concrete failure cases rather than reassurance, they force a verdict on whether a test earns its maintenance cost, and several instruct the model to say when a suite is already adequate instead of inventing gaps. Use them on code you are about to ship, a test that fails once a week, or a suite you have stopped trusting.
36 prompts in 5 groups
Working out which behaviours, edge cases and error paths nothing currently checks.
Unit or integration, what to skip, fixture design, and pruning a suite that costs too much.
Judging naming, mocking, and whether a test asserts behaviour or just the implementation.
Diagnosing a red run, stabilising a flake, and locking a fixed bug in with a regression test.
Manual QA, exploratory charters, accessibility, load, and contracts between services.
Send a prompt you keep coming back to. A person reads every one.
Suggest a prompt