scenario-test-designlisted

# Scenario Test Design Skill ## Overview **Scenario Testing** is a **black-box test design technique** (ISTQB) that structures test cases around **real-world business workflows** from the end-user's perspective. Each scenario describes a connected sequence of actions that reflects a complete business process or user journey — rather than testing individual features in isolation. As defined by Cem Kaner, who formalized the technique: _"A scenario test is a narrative about how the program will be used, besides emotional, social and business contexts, that gets stakeholders to care about failures."_ ### Scenario Testing is a technique, not a test level This is a critical distinction. Scenario Testing is a **test design technique** — it describes _how_ test cases are derived (from user journeys and business workflows), not _where_ they run in the test pyramid. The technique makes no assumption about test level or execution medium: the same design approach applies whether the scenarios will be executed as manual tests, UI automation, API tests, mobile tests, or desktop tests. ### Scenario vs Scenario-Based Test Case In the original Kaner literature, a **scenario** is a high-level narrative describing a realistic user situation, goal, and context. A **scenario-based test case** is the concrete realization of that scenario: specific preconditions, step-by-step actions, and measurable expected results. This skill produces **scenario-based test cases** — scenarios developed to