playwright-skill

Automate end-to-end browser tests by using a skill that detects running local dev servers across common ports, parameterizes the target URL, and launches a visible Playwright browser to execute interactions like login flows and form submissions.

Playwright browser automation works in CI pipelines by creating specific execution contexts, applying configurable HTTP headers, and running temporary scripts via a controlled wrapper with built-in error handling and retry logic.

Capture screenshots during responsive web testing by launching a visible Playwright browser, executing helper utilities to navigate target URLs, and saving the resulting page captures directly to the system temp directory.

The browser automation tool detects multiple running dev servers by automatically scanning common local ports, surfacing all discovered server choices so you can select the correct target URL for your QA task.

To validate login flows and check for broken links, web-testing automation requires a target URL, configurable HTTP headers if needed, and temporary Playwright scripts executed via a run.js wrapper that includes utilities for safe clicking and typing.

E2e-testing scripts written to the temp directory operate with safe, visible execution by default and rely on a controlled wrapper, meaning complex interactions may require custom scripting within the provided helper utilities and error handling constraints.