QA Test Plan Generator

The QA Plan You Skip Today Is the P0 Incident You Get Tomorrow

In September 2023, a routine config change at Optus, Australia's second-largest telco, knocked 10 million customers offline for fourteen hours. The root cause wasn't exotic. It was a network routing update that hadn't been tested against a known edge case. Someone skipped the test plan.

Every PM has shipped something without proper QA coverage. Sometimes you get lucky. Sometimes you don't.

Testing Is a Product Decision, Not Just an Engineering One

Here's what most PMs get wrong about QA: they treat it as an engineering concern. "The engineers will write tests." But engineers test what they built. A QA test plan tests what the user experiences — and those are different things.

The 2024 World Quality Report from Capgemini found that 60% of organizations still discover critical defects in production, and the average cost of fixing a post-release bug is 6x higher than catching it during development. Yet QA planning is the first thing that gets cut when timelines get tight.

The PM's job isn't to write test cases. It's to define what "working" means from the user's perspective. What are the critical user flows? What browsers and devices matter? What accessibility standards do you need to meet? What happens when the API returns a 500? These are product decisions disguised as testing decisions.

How This Prompt Helps

This prompt generates a structured QA test plan from your feature context. You specify the feature, platforms, key user flows, and risk areas — and it produces functional test cases, edge case scenarios, regression checks, cross-browser/device testing matrices, performance benchmarks, and accessibility checks.

The edge case coverage is where this really shines. It systematically walks through failure modes that PMs typically miss: what happens with empty states, maximum input lengths, concurrent users, network timeouts, and permission boundaries.

When to Reach for This

• You're shipping a feature next week and realize nobody's written a test plan
• A critical flow has changed and you need to update regression test coverage
• Your team is expanding to new platforms (mobile, tablet) and needs device-specific test scenarios
• You've had a recent production incident and want to make sure your QA process catches similar issues going forward
• An accessibility audit is coming and you need to proactively test against WCAG guidelines

What Good Looks Like

A good QA test plan is organized by priority (P0 smoke tests you run every release, P1 feature-specific tests, P2 edge cases). Each test case has clear preconditions, steps, and expected results. The plan explicitly covers negative paths — not just "user logs in successfully" but "user enters wrong password five times." It's a document QA engineers can execute without asking follow-up questions.

Sources

• World Quality Report 2024 — Capgemini
• The Cost of Software Defects — NIST