Playwright

Playwright is a browser-automation and testing framework that drives Chromium, Firefox, and WebKit from a single API, enabling reliable end-to-end testing of…

  • AI
  • Development
Playwright is a browser-automation and testing framework that drives Chromium, Firefox, and WebKit from a single API, enabling reliable end-to-end testing of modern web applications.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

82/100 Excellent

Maintained
100last commit 4 days ago
Popular
100100,427 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked today

GitHub stars
100,427
Open issues
68
Last commit
2026-11-17
Latest release
v1.65.1
License
Apache-2.0
Activity
steady

Checked 4 days ago - source: GitHub (microsoft/playwright)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install a browser with OS dependencies Run `npx playwright install --with-deps chromium` before running Chromium tests. It downloads the browser and the required system libraries in one step, so tests do not fail because a browser or dependency is missing. source
  • Install only the browsers you need If you only use Chromium, use `npx playwright install chromium --with-deps` instead of installing every browser. This saves disk space and download time, but make sure you still install any other browser your tests use. source
  • Check supported browser names Run `npx playwright install --help` to see the supported browser names. This helps avoid typos or wrong names that can make Playwright fail to find the browser you want to install. source

Fetched 53 days ago - each note links to its source

Alternatives (2)

  • Selenium - Selenium is a suite of tools specifically for testing web applications.
  • puppeteer - Puppeteer is a Node library which provides a high-level API to control headless Chrome or Chromium over the DevTools Protocol.

Checked 54 days ago - source: AlternativeTo

Common questions

How do I install Playwright's Chromium browser with the required OS dependencies?

Run npx playwright install --with-deps chromium before running Chromium tests. It downloads the browser and required system libraries in one step, so tests do not fail because a browser or dependency is missing.

How can I reuse login authentication state across Playwright tests?

Save authentication state once using page.context().storageState with a path such as auth.json. Reuse that saved state in other tests with test.use and the same storageState path.

How can I make Playwright test selectors more resilient?

Use locators that mirror how users see the page, such as getByRole, getByLabel, getByPlaceholder, and getByTestId. This avoids brittle CSS paths.

What should I check if Playwright tests fail in CI but pass locally?

Check for flaky tests, timeout issues, browser setup problems, and unstable pipelines.

Answers sourced from github.com, playwright.dev, playwright.dev, software-testing-tutorials-automation.com

Community

Collected 48 days ago - public community threads