Describe each behaviour as a scenario: the context (Given), the action (When) and the expected outcome (Then). The builder formats the steps with And, aligns examples tables and exports Gherkin you can drop into Cucumber, SpecFlow or Behave.
Runs entirely in your browser. Nothing is uploaded to any server.
Product, developers and testers agree on behaviour before coding.
Every scenario is a concrete check that proves the story is done.
Gherkin output can drive automated tests directly.
Each scenario should describe one behaviour with one action. Write steps from the user's point of view, in business language, and keep UI details like button colours out unless they matter.
Then steps must be observable: a message appears, an email is sent, a total changes. Avoid vague outcomes like "it works correctly".
Context or starting state.
The single action or event.
Observable, verifiable outcome.
A structure from Behaviour-Driven Development. Given sets up the starting state, When is the action or event, and Then is the observable outcome.
A template scenario run once per row of an Examples table. Use placeholders like <email> in steps and give the values in the table, one column per placeholder.
Put the column names on the first line and one example per line, separated by | or commas. The builder aligns it for you.
Steps that apply before every scenario in the feature, such as "Given I am logged in". They are written once at the top.
Ideally one. Several actions usually mean the scenario is testing more than one behaviour.
More free tools from My Panda Toolbox.