What is Given/When/Then Format?

Given/When/Then — sometimes called Gherkin syntax or BDD (Behavior-Driven Development) format — is a template for writing acceptance criteria and test cases in plain English that is both human-readable and machine-parseable. The three clauses work together: "Given" establishes the context or precondition before an action occurs; "When" describes the specific action or event; "Then" specifies the observable outcome that should result.

A concrete example helps illustrate the format: "Given a logged-in user on the checkout page, When they enter a valid credit card and click 'Pay', Then they should see an order confirmation page and receive a confirmation email." This single criterion captures the who, the action, and the measurable result in a form that a developer, tester, and non-technical stakeholder can all understand and agree on.

The format's power lies in its precision without technical jargon. Because each criterion has a defined starting state, a specific trigger, and a verifiable outcome, there is little room for ambiguous interpretation. Developers know exactly what behavior to implement; testers know exactly what to verify; product owners can read criteria without needing technical knowledge. Tools like Cucumber can even execute Given/When/Then steps directly as automated tests, creating a living specification that proves the system behaves as described.

Codepylot's AI story rewrite feature automatically generates acceptance criteria in Given/When/Then format for every story it produces. When an AI coding agent picks up a story, it uses these structured criteria as a precise specification — each "Then" clause is a test it knows it must satisfy. This tight loop between human-readable criteria and automated implementation is one of the key reasons AI agents produce higher-quality output when working with well-structured stories compared to loose, informal descriptions.