Specification by Example is an agile approach to delivering software where the requirements are defined as executable specifications. Teams identify the scope of the work and illustrate the intended behaviour through examples. The key examples are refined into executable specifications which are then turned into automated tests. These test can then act as living documentation for the software. In order to provide human readable tests for the living documentation, tests may be written in Gherkin based frameworks or other frameworks such as Concordion or FitNesse. The methodology has significant overlap with BDD and ATDD.
Specification by Example (SBE)
Definition: Specification by example is a way of defining requirements using concrete examples, such as sample files, messages or data screens, rather than abstract descriptions alone. The examples clarify what's needed and can become automated acceptance tests.
So what? Asking for real examples pushes the hardest questions back to the business early. A piece of data nobody can specify often reveals that a whole requirement is problematic, before money is spent building it.
Examples: Refusing to start building a payment channel until example messages for each use case are agreed. Asking for mock-ups of data screens before writing acceptance tests.
Getting tests that catch real failures is the hard part. Watch the recording now on demand!
Explore MoT
Tue, 19 Jan 2027
Test Forward is one afternoon at Station F with the QA and engineering people closing that gap in their own teams.
Boost your career in software testing with the MoT Software Testing Essentials Certificate. Learn essential skills, from basic testing techniques to advanced risk analysis, crafted by industry experts.
Into the MoTaverse is a podcast by Ministry of Testing, hosted by Rosie Sherry, exploring the people, insights, and systems shaping quality in modern software teams.