Manual Test Plan Audit for a Release
Check that a release checklist finds what matters.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Audit a manual release test plan. Paste the test plan or checklist: [TEST_PLAN]. Devices and browsers supported: [PLATFORMS]. Bugs found after the last three releases: [POST_RELEASE_BUGS]. Check whether the plan covers critical journeys, data states, permissions, upgrades, accessibility and error cases, whether steps are clear enough for a newcomer, and whether the bugs found later would have been caught. Suggest what to automate. Return a table with Area, Covered?, Gap and Addition, a time estimate for the revised plan from my numbers, and a sign-off template. Also suggest how to rotate testers so that fresh eyes find new issues, how to record results for traceability, and which checks to add for accessibility and slow networks. Add a policy for stopping a release when a blocking defect is found. Finish with a short list of the checks that take the most time but find the fewest problems, and the ones that are quick but find the most, so that the plan can be rebalanced. Suggest a way to time each part.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into ChatGPT, Gemini, Claude or another assistant.