--- name: test-scenarios description: "Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation." --- # Test Scenarios Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step test actions, and expected outcomes. **Use when:** Writing QA test cases, creating test plans, defining acceptance test scenarios, or validating user story implementations. **Arguments:** - `$PRODUCT`: The product or system name - `$USER_STORY`: The user story to test (title and acceptance criteria) - `$CONTEXT`: Additional testing context or constraints ## Step-by-Step Process 1. **Review the user story** and acceptance criteria 2. **Define test objectives** - What specific behavior to validate 3. **Establish starting conditions** - System state, data setup, configurations 4. **Identify user roles** - Who performs the test actions 5. **Create test steps** - Break down interactions step-by-step 6. **Define expected outcomes** - Observable results after each step 7. **Consider edge cases** - Invalid inputs, boundary conditions 8. **Output detailed test scenarios** - Ready for QA execution ## Scenario Template **Test Scenario:** [Clear scenario name] **Test Objective:** [What this test validates] **Starting Conditions:** - [System state required] - [Data or configuration needed] - [User setup or permissions] **User Role:** [Who performs the test] **Test Steps:** 1. [First action and its expected result] 2. [Second action and observable outcome] 3. [Third action and system behavior] 4. [Completion action and final state] **Expected Outcomes:** - [Observable result 1] - [Observable result 2] - [Observable result 3] ## Example Test Scenario **Test Scenario:** View Recently Viewed Products on Product Page **Test Objective:** Verify that the 'Recently viewed' section displays correctly and excludes the current product. **Starting Conditions:** - User is logged in or has browser history enabled - User has viewed at least 2 products in the current session - User is now on a product page different from previously viewed items **User Role:** Online Shopper **Test Steps:** 1. Navigate to any product page → Section should appear at bottom with previously viewed items 2. Scroll to bottom of page → "Recently viewed" section is visible with product cards 3. Verify product thumbnails → Images, titles, and prices are displayed correctly 4. Check current product → Current product is NOT in the recently viewed list 5. Click on a product card → User navigates to the corresponding product page **Expected Outcomes:** - Recently viewed section appears only after viewing at least 1 prior product - Section displays 4-8 product cards with complete information - Current product is excluded from the list - Each card shows "Viewed X minutes/hours ago" timestamp - Clicking cards navigates to correct product pages - Performance: Section loads within 2 seconds ## Output Deliverables - Comprehensive test scenarios for each acceptance criterion - Clear test objectives aligned with user story intent - Detailed step-by-step test actions - Observable expected outcomes after each step - Edge case and error scenario coverage - Ready for QA team execution and documentation