Write verifiable Given / When / Then criteria
Vague acceptance criteria get argued over during acceptance testing, while precise scenarios can be checked, by a tester or by a coding agent. This lesson teaches you to write rigorous Given/When/Then scenarios that the whole team can read and that turn easily into automated tests.
Lesson objective
By the end of this lesson, you will be able to write verifiable, declarative Given/When/Then scenarios (minimal context, a single event, observable outcomes), name them by what sets them apart and group variants into a table of examples.
Topics covered
- Given When Then
- acceptance criteria
- BDD
- Gherkin
- test scenarios
In the glossary
Where it fits
Criteria, edge cases and requirements
How do you write criteria you can verify, and not forget what happens when things do not go as planned?
Lessons in this module
- Write verifiable Given / When / Then criteria (this lesson)
- Edge cases and non-functional requirements
What you will learn in this module
This lesson is part of the course Write specs that developers and AI agents understand
- Write verifiable, declarative and unambiguous Given/When/Then acceptance criteria, including as tables of examples.
- Identify edge cases and non-functional requirements (performance, security, accessibility, personal data) and make them testable.
Related courses
- Product ManagementJuniorSome basics are useful: introductory knowledge of the topic.
Design and validate a product experience with AI
2 hr 30 min
- Product ManagementAdvancedRegular practice: you already use the tools or work on this topic.
Instrument a product and use data to make decisions
3 hr 30 min
- Product ManagementAdvancedRegular practice: you already use the tools or work on this topic.
Prioritize and build an outcome-based roadmap
2 hr 30 min