execute-bdd-scenarios

Solid

Execute BDD test scenarios from .feature files using browser automation.

Testing & QA 12 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
37
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Execute BDD scenarios ## Instructions - Use `mcp__plugin_story-flow_playwright__*` tools to manipulate browser to EXECUTE the BDD scenarios directly without generating any Playwright test file. - **Test Execution Protocol:** - **Before executing:** Read the feature file and confirm the exact line numbers, scenario title, background sections and all "Then" and "And" assertions. - **Execution order is CRITICAL:** 1. **Scenario tags FIRST** (e.g., `@purge-data`) 2. **Background steps SECOND** (setup prerequisites) 3. **Scenario steps THIRD** (Given/When/Then) - **Execute all Background steps:** Background sections (both global and rule-specific) in feature files define prerequisite setup steps. **EVERY** step MUST be completed before executing the scenario steps, including both UI interactions and API calls by curl. - **During execution:** Compare actual behavior against expected behavior at each assertion step. - **On failure:** STOP immediately and provide a summary including: - Expected behavior (with line numbers from feature file) - Actual behavior (with evidence from page snapshot) - Root cause analysis - **CRITICAL: Do NOT continue to subsequent test steps after a failure** - **Executing Multiple Scenarios:** When executing multiple scenarios (e.g., "Execute all scenarios in @path/to/file.feature", "Execute ARMR-01,ARMR-02 scenarios in @path/to/file.feature"): 1. Read the feature file to identify all scenario IDs and titles ...

Details

Author
Intai
Repository
Intai/story-flow
Created
7 months ago
Last Updated
today
Language
N/A
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category