Run the tests in the real environment. A generated plan is not evidence that the software works.
Prompt
MetaCyberGuru reviewed
Build a risk-based test plan for [FEATURE]. The requirements, users, environment and known failure history are [CONTEXT]. Map each important requirement to happy-path, boundary, failure, security and accessibility tests. Rank tests by impact and likelihood. Ask for missing acceptance criteria instead of inventing them. Include test data, expected results and the evidence required to mark each test passed.
What to customize
[FEATURE]
[CONTEXT]
Expected output
A prioritized test matrix tied to requirements, risks, data and observable pass criteria.
Check before you rely on it
AI output can be incomplete or wrong. Verify facts, run code, check citations and keep private data out of tools that your organization has not approved.
Comments
No comments yet. Add the first useful question or observation.