liveBook · Manning

Result

As explained in Effective Behavior-Driven Development

An outcome is a description of the system state after the behavior of interest has taken place in an example.

An outcome describes the system’s state after the behavior of interest. Together with context and action, it makes an example concrete enough to clarify requirements and build shared understanding. section 3.7

Customer collection order

A customer chooses collection; the system asks them to supply contact details. The request is the outcome: it describes the system’s state after the action. section 8.3.2

In a Gherkin scenario, Then states the expected outcome. Usually one outcome illustrates a rule, but closely related results—such as blocking checkout and explaining an error—can be stated together. section 8.3.6 section 8.6

Then they should be prevented from progressing
And they should be informed of what made the contact details unacceptable

See how preventing progress and reporting the contact-details error work together as related outcomes. section 8.3.6

How Effective Behavior-Driven Development covers it

How deep it goes
Defines outcomes as post-behavior system states and explains when one rule may warrant multiple related results.
Examples
Uses a collection-order contact-details request and paired checkout-blocking and error-reporting results.
What you can do after
Formulate examples that state the system’s expected post-action state and distinguish related results.
How it connects
Connects outcomes to examples, context, action, rules, and Gherkin’s Then step.

Also explained in

Compare how 7 books explain result →

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.