e2e-reverse

name	e2e-reverse
description	Reverse-engineer live web applications into Gherkin specifications for E2E testing and recreation. Use when you need to document existing app behavior, create test scenarios from production apps, generate BDD specifications from live websites, or recreate app features based on observed interactions. Autonomous exploration via Ralph Loop with auto-validation and quality scoring. Requires Playwright MCP server for browser automation.
argument-hint	<setup|start|status|export|cancel|help>
compatibility	Requires Playwright MCP server

E2E Reverse Engineering - Command Router

Parse the first argument to determine which subcommand to execute:

• setup → Read and execute setup.md
• start → Read and execute start.md
• status → Read and execute status.md
• export → Read and execute export.md
• cancel → Read and execute cancel.md
• help → Read and execute help.md
• No argument or invalid → Show quick start below

If a valid subcommand is detected, IMMEDIATELY read and execute that command file. Do not continue reading this file.

---

Quick Start

/e2e-reverse setup      # Configure project (base URL, devices, language)
/e2e-reverse start      # Ralph explores autonomously
/e2e-reverse export     # Generate report

Examples

E-commerce site:

/e2e-reverse setup
# Configure: base_url = https://www.example-shop.com
/e2e-reverse start --max-iterations 20
/e2e-reverse export --format html

SaaS dashboard:

/e2e-reverse start https://app.saas-platform.com
/e2e-reverse status  # Check progress during exploration

Mandatory Requirements

1. BLOCKING: Validate Playwright MCP server availability before starting exploration.
2. BLOCKING: Load and apply settings from .claude/e2e-reverse.config.md.
3. Follow Gherkin best practices (Given/When/Then, feature-oriented, proper tagging).
4. Maintain session state with auto-checkpointing; enable resume on interruption.
5. Prioritize quality over quantity (target 3+ scenarios per feature).
6. Document device-specific behavior separately (do not merge desktop/mobile/tablet).
7. Name feature files after functionality (search.feature, not page1.feature).
8. Capture screenshots for key states, organized by feature.
9. Generate Gherkin specs detailed enough for recreation or test automation.

References

• references/CORE-LOOP.md - Ralph iteration engine (read every iteration)
• references/REFERENCE.md - Gherkin conventions, tag system, config structure
• references/REPORTING.md - Report templates
• references/BROWSER-EXAMPLES.md - Playwright MCP integration examples
• references/GHERKIN-BEST-PRACTICES.md - Writing standards
• references/MODAL-HANDLING.md - Dialog/modal handling

Configuration

Project config stored in .claude/e2e-reverse.config.md:

---
base_url: "https://example.com"
output_dir: "e2e/features"
screenshot_dir: "e2e/screenshots"
max_iterations: 15
language: "ko"
devices:
  - name: desktop
    width: 1920
    height: 1080
  - name: mobile
    width: 375
    height: 667
---

Run /e2e-reverse setup to create or update.