Playwright Browser Automation

Playwright browser automation generates and executes test scripts against local development, staging, and remote QA pages. It writes test code to /tmp for ephemeral execution and uses a run.js wrapper to run deterministic tasks like form filling and login flows while keeping project state clean.

Yes, you can run responsive checks and link validation across different viewports using Playwright. The automation generates scripts that perform deterministic UI checks, enabling regression testing and smoke tests for new features before deployment to staging or production environments.

Yes, you need Node.js and the Playwright library installed to execute e2e testing scripts. The skill requires running npm run setup in the skill directory to install dependencies before detecting dev servers and writing test scripts for browser automation tasks.

Dev server detection automatically identifies running local development servers to target them with web testing automation. You can detect servers by running a helper function that outputs JSON configurations, allowing the generated Playwright test scripts to target the correct local endpoints.

To keep project directories clean when running QA automation scripts, this approach writes all generated Playwright test code to the /tmp directory. This ephemeral execution strategy ensures temporary test files do not pollute your main project repository structure.

To execute a generated Playwright test script, navigate to the skill directory and run node run.js followed by the path to your script in /tmp. This wrapper handles the ephemeral execution of the test code against your target web application.