Playwright is aligned with the modern browsers architecture and runs tests out-of-process. This makes Playwright free of the typical in-process test runner limitations.

The playwright.config centralizes configuration: target browsers, timeouts, retries, projects, reporters and more. In existing projects dependencies are added to your current package.json.

Playwright comes with three Playwright Test Agents out of the box: 🎭 planner, 🎭 generator and 🎭 healer. These agents can be used independently, sequentially, or as the chained calls in the agentic loop.

Playwright tests are simple: they perform actions and assert the state against expectations. Playwright automatically waits for actionability checks to pass before performing each action.

The Playwright VS Code extension brings the power of Playwright Test directly into your editor, allowing you to run, debug, and generate tests with a seamless UI-driven experience.

Playwright module provides a method to launch a browser instance. The following is a typical example of using Playwright to drive automation:

The Playwright library can be used as a general purpose browser automation tool, providing a powerful set of APIs to automate web applications, for both sync and async Python.

Playwright was created specifically to accommodate the needs of end-to-end testing. Playwright supports all modern rendering engines including Chromium, WebKit, and Firefox.

Playwright can run tests on Chromium, WebKit and Firefox browsers as well as branded browsers such as Google Chrome and Microsoft Edge. It can also run on emulated tablet and mobile devices.

Playwright Agents, Plan, generate and fix Let AI explore your site and write tests with Playwright MCP How to Generate Playwright Tests using MCP + GitHub Copilot Playwright MCP: How AI Agents Can …