Given/When/Then format
The Given/When/Then format structures a behavioral scenario into initial context, triggering action or event, and expected outcome.
BDD in Action, Second Edition
Given-When-Then notation is a structured scenario format for expressing preconditions, an action or event, and the expected outcome.
- How it is used
- Turns stakeholder examples into shared scenarios for clarifying requirements and expressing expected behavior.
- How deep it goes
- Explains each clause, relevant preconditions, and focused extensions; defers automation and implementation.
- Examples
- Uses account transfers, revised train departures, flight points, and booking changes to make scenarios concrete.
- What you can do after
- Practice/perform writing concise, business-readable scenarios that can become executable acceptance tests.
Read how BDD in Action, Second Edition explains Given/When/Then format →
Shipping Go: Develop, deliver, discuss, design, and go again
A behavioral-specification format that expresses a scenario as an initial context, an action or event, and an expected outcome.
- How it is used
- Structures business behavior as readable scenarios for unit tests, integration tests, and shared development requirements.
- How deep it goes
- Explains context, action, and outcome through translation examples, then connects the format to Gherkin and automated validation.
- Examples
- Uses translation requirements for English, capitalization, whitespace, unsupported languages, and a Gherkin hello-to-German scenario.
- What you can do after
- Apply it via Gherkin and a Go runner to turn readable requirements into validation criteria and automated tests.
Related concepts
- scenarioused by · A scenario is a concrete description of a situation or conditions, often including actions and expected or possible outcomes, for analysis or evaluation.
- Gherkinused by · Gherkin is a structured, human-readable language for expressing software behavior as features, scenarios, and steps such as Given, When, and Then.
- scenario keywordused by · Scenario, also called Example, is a Gherkin keyword that introduces an executable example of expected behavior in a feature file.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.