Specification by Example

Specification by Example is a software development practice that captures requirements as concrete examples which then serve as both automated tests and living documentation.

1 articleLast mentioned

Specification by Example is a software development practice in which requirements are defined as concrete examples with inputs and expected outcomes rather than abstract descriptions, and those examples are used both as automated acceptance tests and as living documentation that stays current. It became widely known through consultant Gojko Adzic's 2011 book of the same name, which distilled the practices of many teams.

It emphasizes a collaborative process in which business stakeholders, developers, and testers create the examples together, and it is closely tied to BDD, ATDD, and techniques such as Example Mapping. Because examples are treated as executable specifications, it is used as a way to reduce ambiguity in requirements.

This entry is based on AIPOST articles and widely known facts. If something is wrong, please send us a correction request.

Articles covering this entry

  • Example Mapping Plus TDD Lifts AI Agent Code Correctness From 27% to 94%AI in Practice ·

    …rstood as Example-Guided Development, an umbrella that also covers acceptance test-driven development, behavior-driven development and specification by example.

    Read article

Found a mistake or missing an entry?

Wiki entries are based on AIPOST articles and widely known facts. If an entry is wrong, send us a correction request and we will check and fix it. Names from new articles are added to the wiki after the article is published.