Speed Up a Slow Test Suite
Coding
Cut test runtime without weakening coverage or changing behavior. Inspired by Forward Future's Loop Library.
Prompt
Step 1 — Measure the baseline Record the current suite runtime and coverage. Ask the AI to identify the slowest tests and likely causes. Step 2 — Optimize one thing Apply a single speedup (parallelize, remove redundant setup, mock a slow dependency). Keep the behavior identical. Step 3 — Prove nothing broke Re-run the full suite. Confirm it is faster, still passes, and coverage did not drop. Step 4 — Repeat until fast enough Keep improving while each change measurably helps. Stop when the suite is fast enough or gains flatten out.
Use this prompt in AIniverse
Tap to copy, run it on ChatGPT / Claude / Gemini, save to your stack, or remix.
Open in AppMore Coding prompts
Independent Verifier Pass
When implementation claims done, a separate verifier pass runs build, lint, and tests with no access to the implement...
API Contract Until Match
Loop until API responses match the OpenAPI or JSON Schema contract — catch drift between docs and implementation.
De-Sloppify Pass
After implementation, run a cleanup pass: remove debug code, tighten naming, delete dead branches, and align with pro...
Merge Conflict Resolver
Rebase or merge target branch, resolve conflicts file by file, and loop until the branch is current and tests pass.