Guides › Documents & Data
Write a test plan straight from the requirements
A test case table covering happy paths, edge cases and failures, generated from your requirements and ready to track in a spreadsheet.
When to use it
Once requirements are agreed and before testing starts
Step by step
Gather the requirements
Open the agreed requirements or acceptance criteria in Google Docs and copy them.
Ask for test cases
Paste this into your AI assistant.
Prompt to copyHere are the acceptance criteria for a feature: [paste]. System notes: [platforms, user roles, integrations]. Write a test plan as a table with columns: ID, requirement it covers, test type (unit / integration / end-to-end / manual), preconditions, steps, expected result, priority (High/Medium/Low). Include happy paths, boundary values, invalid input, permission checks for each user role and what happens when a dependency fails. Finish with a coverage check listing any requirement with no test, and suggest which tests are worth automating first.Put it in a sheet
Paste the table into Google Sheets and add Status and Notes columns so the team can track results.
Turn the top tests into code
For the high-priority automated cases, ask the assistant to draft test functions in your test framework, then review and adapt them to your codebase.
What you get
TC-07 | Export orders | Integration | User has 0 orders | Click Export | Empty CSV with headers only | Medium. TC-08 | Export orders | Manual | Viewer role | Open Orders | Export button hidden | High.
Tips
- Ask for a second pass focused only on what a malicious or confused user might do; it often finds cases the first pass missed.