Features
Everything Provo does
Provo reads a spec (pasted, uploaded, or imported from GitHub or Linear), splits it into requirements with their exact words and line numbers, and drafts test cases that each quote their requirement. You review, organize, run and export them, and when the spec changes Provo shows what changed and which cases to review. Everything below is built.
Specs in
- Paste or upload. Markdown, plain text, PDF or Word (.docx), up to 10 MB.
- GitHub. Import an issue or a pull request description, browse a repository's open issues or pull requests, and fetch the latest text again as a new version. Sign in with GitHub (OAuth) or use a fine-grained token.
- Linear. Import an issue by identifier or from a team's recent issues with a personal API key. Read only.
- Requirements with locations. Every requirement keeps its exact words, its section heading and its line numbers, shown next to the spec text.
Test generation
- Traced cases. Steps with expected results, preconditions, priority and tags, each case quoting the requirement it came from.
- Every kind of case. Functional, edge, negative and regression scenarios, and acceptance criteria in Given/When/Then form.
- Questions, not guesses. Vague words, missing numbers and missing error behavior are listed as open questions you can answer or dismiss.
- Tailored to what you test. Web app, API or mobile app per project, plus your team's own testing notes, within what the spec says.
- Regenerate one case. Ask for a change in plain words; the new version must still quote its requirement and comes back as a draft.
Suite management
- Review. Draft, approved and rejected, one at a time or in bulk. Rejected cases stay out of runs and exports.
- Organize. Folders and sub-folders, tags, priorities, search and filters.
- Write your own. Hand-written cases can be traced to a requirement too.
Traceability and change
- Traceability matrix. Requirement, test case and latest run result, with gaps and failures one click away. Exports as CSV.
- Spec versions. A line diff of the old and new spec, requirements marked new, changed or removed, and the cases traced to changed or removed ones marked for review with the reason.
- Generate for what changed. One button drafts cases for only the new and changed requirements.
Runs
- Execution records. Pass, fail, blocked or skipped, notes, who ran it and when, per environment and build.
- Assignees. Assign cases to teammates; they get an email and an "only mine" view.
- GitHub, on confirmation. Create an issue for a failed case or post a run summary to a pull request, each after you see the exact text.
Exports and your data
- Four formats. CSV, Markdown, Gherkin .feature and JSON, with the trace and open questions in every one.
- Workspace export and deletion. Download everything as JSON; delete a spec, project, run or the whole workspace.