You change something in your store or contact form and only find out it broke when a customer stops writing. Playwright drives Chromium, Firefox and WebKit like a person would: it visits, clicks, fills fields and tells you when something fails. There is also a version that lets an AI agent browse your site for you.
Who this is NOT for
If your site is a Wix or Shopify template that neither you nor anyone on your team codes, do not install this: you have no code to protect, and checking your form by hand once a week will do. If what you want is moving data between apps (WhatsApp to a spreadsheet, email to calendar), use n8n. This is a developer tool, even with Microsoft behind it and 97k stars.
It is now five products under one name (Test, CLI, MCP, Library and the VS Code extension), and most people waste their first afternoon picking the wrong one. For a small business already working with a coding agent, the way in is MCP or the CLI, not the test runner. Its own README says the CLI uses fewer tokens than MCP. The most common mistake is finding buttons by CSS paths that break with every redesign. The project recommends finding them the way a person sees them (getByRole, getByLabel), and you should listen. It is actively maintained: the last commit is from today and it is not archived.
Your first step
If you already use Claude Code, run claude mcp add playwright npx @playwright/mcp@latest and ask it to open your site, fill in your contact form and tell you which step fails.
The Playwright implementation guide
The project belongs to Microsoft and it is free: the link beside asks for nothing. The guide to set it up without getting lost is ours: step by step, common mistakes and a checklist. Leave your email and we will send it.
No spam. Unsubscribe anytime.