Use cases
Test cases from PRDs, for product teams shipping web apps
Provo turns a web app PRD into test cases before the sprint starts. Paste or upload the PRD, or import the GitHub or Linear issue; Provo splits it into requirements and drafts functional, edge and negative cases for permissions, validation, limits and flows, each quoting its requirement. Unclear behavior becomes a question for the product manager.
Where it fits in a sprint
- Planning: import the PRD or ticket; open questions go back to the product manager before work starts.
- Review: approve, edit or reject cases; group them in folders by area, tag them, set priorities.
- Testing: start a run against an environment and build; record pass, fail, blocked or skipped with notes; assign cases to testers.
- Release: post the run summary to the pull request after reviewing it, and export the suite for your records.
What it covers for web apps
Projects marked as web apps steer generation toward roles and permissions, form validation, limits and boundaries, empty and error states, and multi-step flows, but only where the spec states them. Nothing about browsers or devices is invented; add your browser matrix to the workspace's testing notes.
When the PRD changes
Add the new version, or fetch the ticket again. Provo shows the diff, keeps cases for unchanged requirements and marks the ones traced to changed or removed requirements for review, so the regression suite follows the PRD.
Questions
Do we need to change how we write PRDs?
No. Provo reads list items, table rows and paragraphs under headings. Clear headings and one requirement per bullet give the cleanest traces, and context sections such as Background are skipped.
Can testers edit what the AI drafts?
Yes. Every case can be edited, approved, rejected or regenerated with an instruction; regenerated cases come back as drafts.