What problem does it solve? Writing integration and end-to-end tests usually means guessing selectors, hardcoding URLs, and booting duplicate test environments, which produces brittle tests and slow runs. This Skill explores the running application first, reuses a shared test environment, and reports failures with per-test artifact-based diagnosis. ## Core Features & Use Cases - Exploration-driven test authoring: Drives the configured browser provider (open, snapshot, interact, assert) against the live app so tests use only observed roles, labels, and text — never guessed CSS selectors. - Shared test environment reuse: Attaches to the validated test-env.json descriptor written by om-prepare-test-env (PID check, readiness probe, freshness TTL) instead of booting a second instance, with credentials referenced via environment variables rather than hardcoded values. - Artifact-based failure analysis: Classifies every failure as product regression, test issue, or environment issue using screenshots, traces, and error context, and reports a per-test table with suggested owner and next action. - Use Case: After implementing a company-creation flow, ask the agent to write integration tests; it attaches to the running shared environment, walks the flow in the browser, authors a Playwright or agent-browser test following the repo's conventions, verifies it passes, and cleans up its fixtures. ## Quick Start Ask the agent to create and run integration tests for the login flow using the om-integration-tests skill against the shared test environment.
