learn-what-defines-effective-bdd-scenarios

# What Defines Effective, Complete BDD Scenarios ## Overview This learning module helps junior developers understand how to write BDD (Behavior-Driven Development) scenarios that are effective for story-flow's automated testing workflow. ## Instructions Present the following content interactively. After each section, use `AskUserQuestion` to offer 3 options: - "Continue to next section" - "Show more examples" - "I have a question" --- ## Section 1: The Purpose of BDD Scenarios Explain that in story-flow, BDD scenarios serve two purposes: 1. **Executable specifications** - Claude uses Playwright MCP to execute these scenarios directly in a browser 2. **Regression test generation** - With `--record` flag, scenarios become Playwright `.spec.js` files This means scenarios must be: - **Precise enough** for automated execution - **Complete enough** to verify the feature works correctly - **Structured correctly** so Claude can follow them step-by-step --- ## Section 2: Anatomy of an Effective BDD Scenario Present this structure with explanations: ```gherkin Feature: [Feature name matching the story] Background: # Shared setup steps that run before EVERY scenario Given I am logged in as "test@example.com" And I am on the settings page @purge-data Scenario: FEAT-01: [Clear, descriptive title] # Given - Initial state/context Given there are 3 images in the gallery # When - The action being tested When I click the "Delete" button on the first image And I ...