e2e-acceptance

Automated headless acceptance testing executes end-to-end tests without a visible browser UI, making it ideal for CI/CD pipelines. This Skill runs tests automatically after code commits to verify core application functionalities before deployment.

Playwright captures diagnostic data during e2e testing when business logic failures occur. It extracts page layout, text content, and network requests from the headless browser state to provide debugging information for failed acceptance tests.

Python and Playwright are required to run headless e2e tests and capture page state. The Skill relies on these dependencies to execute automated test scripts and perform browser-based diagnostic captures upon failure.

A degradation strategy provides a fallback mechanism for running acceptance tests by attempting the primary `rscore` entry point first. If `rscore` fails, it automatically degrades to executing `python main.py` to ensure test robustness.

E2e tests capture network requests during business logic errors by leveraging MCP Playwright integration. If capture fails, it typically indicates the headless browser environment was not properly initialized before the test execution reached the failing state.

Headless acceptance testing works for both development and user modes. Running the Skill performs automated end-to-end test execution across both operational modes to ensure comprehensive application validation before deployment.