playwright-skill

You can automate browser testing by auto-detecting running dev servers and generating deterministic Playwright scripts against the detected URLs. The skill writes these test scripts to a temporary directory to avoid cluttering your project and executes them via a universal runner.

The best way to automate web testing cleanly is to generate your automation scripts in a temporary directory such as /tmp. By writing generated test files outside your project root, you maintain a clean workspace while still executing repeatable browser-driven workflows.

Yes, you can run Playwright automation scripts with visible browser sessions and custom headers. The executor enforces safe defaults like visible browsers and environment-driven headers, while also offering optional headers for tracing and direct control over target URLs.

Browser automation supports multi-browser testing for validating workflows like login flows, link checking, and responsive UX checks. You can capture artifacts such as screenshots and logs during execution to validate application behavior across different simulated devices.

To generate and execute repeatable web-testing scripts, describe your browser task and the system will create a script in the /tmp directory. A universal executor then runs the file with deterministic options to capture artifacts and validate QA workflows consistently.

When automating browser tasks in local development environments, limitations include relying on the auto-detection of currently running dev servers. Execution is designed for local validation with visible browser sessions rather than fully headless background processing or remote production environments.