Playwright MCP vs CLI vs Agents: What to Use in 2026
Playwright has three ways to talk to AI: MCP, CLI, and Test Agents. Here's the decision framework an enterprise SDET uses to pick the right one for 2026.
Playwright has three ways to talk to AI: MCP, CLI, and Test Agents. Here's the decision framework an enterprise SDET uses to pick the right one for 2026.
Playwright 1.59 ships --debug=cli and scriptable trace analysis. The first debug surface that actually works where enterprise tests fail — headless CI.
Playwright 1.59 ships a Screencast API with burned-in action annotations and chapter markers. Microsoft sells it for AI agents — the real win is CI triage.
How we built a Playwright API test data layer in Java — replacing UI setup that burned 150 minutes per run with 3 classes and a legacy API wrapping pattern.
Most Playwright teams still use CSS selectors via locator() out of habit. getByRole and getByText find elements the way users do — and survive redesigns.
How shared test accounts create race conditions in parallel Playwright runs, and the 3 isolation patterns that eliminated our 12% failure rate overnight.
Launching a new browser per test in Playwright wastes 3-6 seconds each time. BrowserContext gives you the same isolation in milliseconds. Here's how to switch.
storageState() saves cookies, localStorage, and sessionStorage in one blob. Here's how it silently poisons parallel tests and how to strip it to cookies only.
We build the exact same Java test in both Selenium and Playwright side by side. See the real code differences in setup, locators, network mocking, and debugging
Your UI tests pass green while the console throws errors. Learn to catch JavaScript and page errors in Selenium and Playwright Java — before users do.
Parallelism alone won't save your slow test suite. Here are five layers of optimization — from test design to cloud infrastructure — ranked by real impact.
Eight Playwright BrowserContexts were properly isolated, but they all loaded the same session cookie — so the server treated 8 parallel threads as one.
Most self-healing test tools use simple fallback chains, not real AI. Learn the 4 approaches to AI locator repair and which one fits your framework best.
Why onceDialog stays registered when no dialog fires, silently eating the next dialog from an unrelated action — and the onDialog/offDialog pattern that fixes it.
How a 'flaky' Playwright test exposed a shared test user race condition in our parallel suite, and the isolation patterns that fixed it for good.
How UnhandledAlertException broke 8-thread parallel execution and why Playwright's event-driven dialog model avoids that entire failure pattern in practice.
How onceDialog fixes permanent handler leaks from onDialog — and the one case where it creates a new problem. Includes the onDialog/offDialog pattern for dialogs that might not fire.
Replace emailed Extent Report HTML files with a persistent Allure portal on Jenkins, so the team gets one URL, full history, and zero downloads to manage.
How Playwright's locator API eliminates the need for custom wrapper classes we spent weeks building in Selenium, and when wrappers still make sense today.
A hands-on experiment with AI-generated Playwright tests: where LLMs save time, where they create false confidence, and the review workflow that works.
Why text-based locators reduce test maintenance by up to 60%, and how to use them in Selenium and Playwright with real enterprise UI examples that last.
An honest take on Cypress vs Playwright migrations from an SDET who's done three, including the signals that tell you not to migrate your suite just yet.
The 3 async mistakes that cause flaky Playwright tests after a Selenium migration, and how we fixed a 23% intermittent failure rate in our CI pipeline.
The real difference between XPath text(), dot, contains(), and normalize-space() for test automation — with examples that explain real flaky failures.
Search is not available in dev mode.
Run npm run build then
npm run preview:local to test search locally.