Results for “playwright-cli”

Automate browser interactions, test web pages and work with Playwright tests.

The English summary is being prepared. Showing the original description.

Use when the task requires automating a real browser from the terminal (navigation, form filling, DOM snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.

The English summary is being prepared. Showing the original description.

Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.

The English summary is being prepared. Showing the original description.

Set a repo up to prove engineering-task work actually works before it ships. Investigates the repo, ensures a one-command dev stack (`dev-local`) exists, asks whether verification runs locally or in a sandbox (crabbox), confirms/installs the driver (the `playwright-cli` skill for web by default). Outputs three artifacts: a committed `/verify` skill (per-task verification SOP — spawn a verifier sub-agent → drive the app → screenshot/video proof → open a PR with the proof embedded), the `/dev-local` skill + script, and the installed driver skill. Use when someone says "set up verification", "make this repo verifiable", "scaffold a verify skill", "set up the verifier".

The English summary is being prepared. Showing the original description.

Session-persistent browser automation via Playwright CLI: form filling, screenshots, data extraction, multi-step flows. NOT for autonomous flows (mk:agent-browser) or .spec.ts E2E code (mk:qa-manual).

The English summary is being prepared. Showing the original description.

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

The English summary is being prepared. Showing the original description.

[Testing] Automate browser interactions, test web pages, and work with Playwright tests.

The English summary is being prepared. Showing the original description.

Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.

The English summary is being prepared. Showing the original description.

Use for deterministic terminal or CI browser automation, repeatable regressions, traces, snapshots, screenshots, and unattended playwright-cli batches. Route interactive or signed-in Chrome work through browser-automation-router first.

The English summary is being prepared. Showing the original description.

Automate browser interactions, inspect web pages, and work with Playwright tests using a headless-first CLI workflow.

The English summary is being prepared. Showing the original description.

Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.

The English summary is being prepared. Showing the original description.

Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.

The English summary is being prepared. Showing the original description.

Playwright v1.64 (E2E / コンポーネントテストフレームワーク) リファレンス。 test, expect, page, locator, getByRole / getByText / getByLabel / getByTestId / getByRef、 toBeVisible, click, fill, route, mock, fixtures、playwright.config.ts、 auth 永続化、Credentials (passkeys / WebAuthn)、WebStorage、WebMCP、 Playwright MCP / playwright-cli、trace viewer、screencast、test locks、codegen、UI モード。

The English summary is being prepared. Showing the original description.

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

The English summary is being prepared. Showing the original description.

Use when the user wants tests planned for existing code or a test audit — unit, integration, E2E scenarios exportable to Playwright, playwright-cli UI checks, a coverage matrix — 'criar testes para o UserService', 'plano de testes E2E do login', 'auditar a cobertura'. Writes .planning/feat/features/{slug}/plan.md. Do NOT use for code review (feat-review), for implementing features (feat-feature) or to run an existing plan (feat-exec).

The English summary is being prepared. Showing the original description.

Use when the user wants a UI-only action plan — components, pages, composables/hooks, state, forms and their E2E coverage — 'plano de frontend para a tela X', 'plan the settings page'. Writes .planning/feat/features/{slug}/plan.md with E2E scenarios and playwright-cli checks. Do NOT use for API/database work (feat-backend), full features (feat-feature), writing code (feat-exec) or UI review (feat-review).

The English summary is being prepared. Showing the original description.

Automate browser interactions, test web pages and work with Playwright tests.

The English summary is being prepared. Showing the original description.