Creating QA Flows
A QA Flow is a set of test cases generated for one application. To create one, open the QA Flows page for your application and click New Flow.
Describe what to test
Section titled “Describe what to test”You can seed a flow two ways:
- Write a description — Describe the behavior you want to test in plain language. The more specific you are, the more focused the generated test cases will be.
- Upload a PRD — Drop in a product requirements document and the agent extracts test cases from it.
You can also add personas to shape the generated coverage — for example, generating cases that exercise a first-time visitor’s onboarding versus a power user’s advanced flows. Personas come from UX Insights.
Generate test cases
Section titled “Generate test cases”When you start generation, the agent reads your input and produces structured test cases. Each test case has:
- Title — A short name for what the case verifies.
- Objective — What the test is meant to confirm.
- Steps — The sequence of actions the agent will attempt.
- Expected outcome — The result that counts as a pass.
- Priority — Low, Medium, or High.
The agent also derives an ultimate goal for the flow — a one-line summary of what the whole set of test cases is trying to validate.
Review and refine
Section titled “Review and refine”Before running anything, review the generated cases. You can:
- Edit a test case directly — change its title, objective, steps, expected outcome, or priority.
- Refine the whole set — give a follow-up instruction (for example, “add a case for the password-reset flow”) and the agent rewrites the test cases accordingly.
- Activate or deactivate individual cases so a run only executes the ones you want.
Test cases keep a version history, so refinements and edits are tracked and can be rolled back later.