Draft From a Requirement
1 min read
A requirement’s detail page has its own Draft with AI button. It writes test cases directly, in one step, without mapping coverage first.
Use it when you already know what you want covered. Use the coverage workspace when you want to see what you are missing.
Draft the cases
Section titled “Draft the cases”-
Open a requirement and select Draft with AI. The requirement you opened is pre-selected.
-
Add more Requirements if the cases should span several.
-
Add Additional context or attach Documents if the requirement text alone is thin.
-
Choose a Focus, a Step format, and How many cases to write.
-
Select Generate drafts.
How it differs from the workspace
Section titled “How it differs from the workspace”| From a requirement | Coverage workspace | |
|---|---|---|
| Coverage map | No | Yes — up to 40 scenarios |
| Focus | One lens per run | Several lenses, plus risk analysis |
| Cases per run | Up to 10 | Up to 20, written in batches |
| Gaps reported | No | Yes, named per requirement |
Everything else is shared. The same grounding rules apply, drafts are edited the same way, and adding them does the same thing — see Write and review and Add them to the repository.
What it knows
Section titled “What it knows”The requirement’s own text is the source, and the titles of test cases already linked to it are sent along, so it proposes cases your suite doesn’t have rather than repeating it.
Because there is no coverage map, there is no gap report here. If you want to know which of your requirements have nothing proposed for them, start from the Repository instead.
After generating
Section titled “After generating”Drafts appear in the same list, with the same controls: tick what you want, expand to edit any field, discard the rest, choose a destination folder, and add.
Accepted cases link back to the requirement automatically, so the requirement’s coverage figures update as soon as they land.