An illustrative scenario turns one concrete example into a business-readable description of a single rule or behavior. It helps stakeholders understand, discuss, and document what the system should do; automated testing is a possible side effect, not its primary purpose. section 6.5 section 7.8
Keep each scenario focused and easy to review:
- Base it on one concrete example that illustrates one rule. The rule may be defined at different levels of abstraction, depending on the stakeholders’ needs. section 6.5
- Write briefly and clearly so stakeholders can understand and review the behavior. section 7.8
- Use precise assertions for detailed behavior, such as a financial calculation. section 6.5
- Keep the focus on one behavior. A journey scenario instead describes how multiple behaviors combine into an overall flow. section 6.5 section 10.7
- Do not convert manual test scripts directly into illustrative scenarios. Analyze them first and retain only valuable behavior documentation. section 11.3.1 section 11.4
A detailed rule, not a whole journey
A scenario could specify whether an order item qualifies for a promotion, or check the result of a financial calculation. Either focuses on a particular behavior rather than describing an entire customer journey. section 6.5
