Free · No sign-up
Write acceptance criteria your team can actually test against
Paste your user stories — or the requirements behind them — and get precise Given / When / Then criteria covering the happy path, the edge cases, and the validations.
How it works
Paste your stories
Already have user stories? Paste them. Only have requirements? Paste those and the stories get written first, so every criterion has something to be 'done' for.
Each criterion stays atomic
Given a precondition, When an action, Then one observable outcome. Split apart, never bundled — a criterion that checks three things at once can only ever half-pass.
The edge cases come too
The happy path is the easy part. You also get the validation failures, the empty states, and the permission checks the story implies but nobody wrote down.
Questions
- How many criteria will each story get?
- Two to five. Enough to cover the success path plus the meaningful failures, and few enough that someone will actually read them before they start work.
- Why Given / When / Then rather than a checklist?
- Because a checklist item like 'validation works' cannot be tested and cannot be disputed. Given / When / Then forces a precondition, an action, and one observable outcome, which is exactly the shape a test case needs and exactly what makes a criterion arguable in a refinement session.
- Can I paste a whole requirements document?
- Yes. It reads the requirements out of it, writes the stories that deliver them, and then writes the criteria for each story. You see all three levels in the result, so you can check its reading before you trust it.
- What happens when the requirement changes later?
- On this page, nothing — it is a one-off document. Saved into a project, each criterion stays attached to its story and its requirement, so when a later meeting revises that requirement you are told which criteria are now out of date instead of finding out in QA.
- Is it free, and do I need an account?
- Free, with no account. Signing up is only needed to save the criteria into a project alongside the stories and requirements they belong to.
What comes next
- Test Case GeneratorTurn those criteria into executable test scripts with steps and results.
- User Story GeneratorStart a level higher and generate the stories themselves.
Or save any of it into a project, where all of this connects up on its own — see every tool.