liveBook · Manning

Specification

As explained in Effective Behavior-Driven Development

A sufficiently complete description of a solution's required behavior and characteristics for a delivery team to design and implement it.

A specification records a shared understanding of how a system should behave in business-readable language. It declares the desired behavior and helps prevent unexpected changes. section 6.0 section 1.5

In agentic development, the specification guides generated code and constrains coding agents. Review its intent carefully: automated tests may not faithfully represent scenario wording, so supplementary testing can help restore confidence. section 4.5 section 4.5

Make readability the priority when wording scenarios. Repetition or pronouns are stylistic choices when meaning stays clear; do not let automation needs make the specification harder to read. Once approved, change a scenario only when system behavior changes. section 9.5 section 9.5

Listing 9.4 Pay-on-collection restricted scenario using they
Scenario: Restricted unauthenticated customer not offered
➥ pay-on-collection option
  Given a restricted customer
  And they are unauthenticated
  When they place an order for customer-collection
  Then pay-on-collection should not be offered as a payment option

A restricted-customer payment scenario shows how a pronoun can keep business-readable wording concise when its meaning is clear. section 9.5

How Effective Behavior-Driven Development covers it

How deep it goes
Explains business-readable formulation, scenario wording, approval, and AI guardrails, while deferring automation details to later treatment.
Examples
Uses a restricted customer ordering for collection scenario to illustrate readable pronoun use.
What it assumes
Builds on shared understanding of system behavior and domain knowledge, developed through requirements discovery.
What you can do after
Apply readable, reviewed scenarios to guide implementation and guard against unintended behavior changes.
How it connects
Connects specifications with BDD, Gherkin, requirements discovery, TDD, and exploratory testing.

Also explained in

Compare how 12 books explain specification →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Behavior-Driven Development. The section links point to the parts of the book it draws on.