Audit intermediate Works with: Any AI

Regression Test Plan for a Risky Change

Table output Has example

Plan a regression test for a risky change: decide what to retest before shipping, ranked by impact and likelihood.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Plan regression testing. Description of the change: [CHANGE_DESCRIPTION]. Components touched: [COMPONENTS]. Existing automated tests: [AUTOMATED_TESTS]. Time available: [TIME_AVAILABLE].

List the areas the change could affect, directly and through shared code or data. For each, say whether an automated test exists, whether a manual check is needed, and the risk if it fails. Prioritise by risk and by effort, and fit the plan to the time available with the arithmetic.

Return a prioritised test list with owner placeholders, a rollback trigger and a short checklist for the first hour after release.

Add a worked time fit: 12 hours available; critical checks need 5 hours; high-risk areas need 4; medium need 5; low need 3. Total 17, over by 5 hours, so cut the 3 low and 2 of the medium, leaving 12. Add a rollback trigger such as error rate above 2 percent for 10 minutes or any payment failure spike. Provide a first-hour checklist after release: dashboards, logs, a manual purchase, and a message to support.

Add a short list of questions to ask before accepting the plan: what is the worst realistic failure, who would notice first, how fast can we roll back, and who is on call during the first day.

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 Any AI or another assistant.

Invented plan. Hours available 12. Critical checks 5 hours; high-risk areas 4; medium 5; low 3. Total 17, which is 5 over.
Cut the 3 low and 2 of the medium: 5 + 4 + 3 = 12 hours.
Rollback trigger: error rate above 2 percent for 10 minutes, or any spike in payment failures.
First hour after release: dashboards, logs, a manual purchase, message to support.
Owners: named for each area.
Re-plan: if the change slips by a day, the 5 cut hours of low-risk checks stay cut; add one hour back for medium-risk areas.

• audit