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






