Manuals / Playwright with Python / Chapter 3
Part 0 · Background · beginner · ~35 min · Chapter 3 of 61
2. What Playwright Can Do
Automate Chromium, Firefox, WebKit — one API, all browsers You write your test logic once, and swap the browser_type (chromium, firefox, webkit) to run the exact same test against a different engine — no rewriting locators or logic per browser. This is a genuinely rare capability; most tools require separate driver setups per browser at minimum, and Selenium historically required different WebDriv
Step 1 of 2
Overview
Automate Chromium, Firefox, WebKit — one API, all browsers You write your test logic once, and swap the browser_type (chromium, firefox, webkit) to run the exact same test against a different engine — no rewriting locators or logic per browser. This is a genuinely rare capability; most tools require separate driver setups per browser at minimum, and Selenium historically required different WebDriver binaries per browser with occasional locator inconsistencies between them. Mobile web emulation (no real device needed) Playwright ships built-in device descriptors (e.g., "iPhone 13", "Pixel 5") that set the right viewport size, user-agent string, touch support, and device pixel ratio automatically. You get realistic mobile-web testing without owning a device lab. Note the important boundary: this emulates mobile web browsers, not native mobile apps — that distinction matters (see Chapter 4 below, "What This Manual Will NOT Cover").
Chapter learning outcomes
- Auto-waiting (no manual sleep/wait hacks)
Clear these before you leave
Side quest
2. What Playwright Can Do deliverable
Apply one idea from “Overview” in a small script or note.