Browser QA

Use the host's browser tools or the project's installed browser runner. Inspect the active tool contract before choosing commands.

Discover

• Read the app's start/test wrappers, Playwright configuration, existing specs, and approved target.
• Prefer native browser control when available. Use the installed CLI when the task needs it.
• Microsoft's published package is @playwright/cli; verify the installed distribution and version with local help.
• Do not assume a local command named playwright-cli has the same flags as another release.

Explore with current state

Capture the page state before acting. Use observed refs or accessible locators. Refresh state after navigation or changes that invalidate the target.

Current Playwright CLI accepts snapshot refs, CSS, and Playwright locators. Prefer refs for inspected interactive exploration and role/test-id locators for maintained specs. Do not invent refs or selectors.

Snapshot output may link to a saved file instead of printing the full tree. Read the returned artifact. Verify output-control flags in the installed help rather than relying on a remembered --raw flag.