Playwright Cli

Interaction and inspection

playwright-cli snapshot
playwright-cli click e3
playwright-cli fill e5 "[email protected]"
playwright-cli type "search text"
playwright-cli press Enter
playwright-cli select e7 "option-value"
playwright-cli check e9
playwright-cli uncheck e9
playwright-cli hover e4
playwright-cli eval "document.title"
playwright-cli eval "el => el.textContent" e5

Output, tabs, and state

playwright-cli screenshot
playwright-cli screenshot e5 --filename=field.png
playwright-cli pdf --filename=page.pdf
playwright-cli tab-new https://example.com/other
playwright-cli tab-list
playwright-cli tab-select 0
playwright-cli state-save auth.json
playwright-cli state-load auth.json
playwright-cli close
playwright-cli delete-data

Working style

• Snapshot before and after meaningful interactions.
• Prefer stable element refs from snapshot output over coordinate-based actions.
• Use named sessions (-s=<name>) only when you need multiple concurrent browsers.
• Use persistent profiles only when explicitly required, and clean them up afterward.
• Use close-all/kill-all only for stuck sessions.

Quick example

playwright-cli open https://example.com/login
playwright-cli snapshot
playwright-cli fill e1 "[email protected]"
playwright-cli fill e2 "password123"
playwright-cli click e3
playwright-cli screenshot --filename=after-login.png
playwright-cli close

Task references

• Request mocking
• Running Playwright code
• Browser session management
• Storage state
• Test generation
• Tracing
• Video recording