explore-app
Explore App
When to use
- After ingest-spec has populated
parsed-spec.mdwith scenarios - Once per scenario — run separately for each scenario in the test plan
- When running as part of
run-testing-sessionpipeline (Stage 2, per scenario) - When exploration is stale after a UI change
Inputs
- Scenario name and slug (from
parsed-spec.md) - Base URL (from
project-context.mdor user-provided) docs/playwright-spec-testing/project-context.md(for baseURL only)docs/playwright-spec-testing/parsed-spec.md(this scenario's section)
What it does
Walk through the app in a browser, performing each step of the scenario, and capture real selectors, URLs, and behavior. No selector is invented — every selector in the exploration report must come from what you observe.
More from lautaroleonhardt/pst
analyze-codebase
Use when starting a Playwright testing session or when project structure is unknown. Scans the project for Playwright config, test conventions, routing, and tech stack. Writes output to docs/playwright-spec-testing/project-context.md.
9plan-tests
Use after explore-app to synthesize an exhaustive, human-reviewable test plan from exploration reports and project context. Reads all exploration/<slug>.md files, parsed-spec.md, and project-context.md. Outputs test-plan.md with full steps, assertions, and assigned test file paths.
9ingest-spec
Use when you have a Gherkin .feature file or plain-English test cases to parse into structured scenarios. Writes output to docs/playwright-spec-testing/parsed-spec.md.
9generate-tests
Use after plan-tests to write a Playwright test for one scenario by mechanically translating test-plan.md into Playwright API calls. Requires docs/playwright-spec-testing/test-plan.md. Writes the test file at the path assigned in the plan.
9debug-test
Use when a Playwright test is failing. Diagnoses the root cause and applies a minimal fix. Requires the failing test file path and the full error output.
9run-testing-session
Use to run the full Playwright testing pipeline (analyze → ingest → plan → explore → generate → debug) with isolated subagent context per stage. Each stage is reviewed and fixed automatically. Requires a running target app and a spec input.
9