4. What This Manual Will NOT Cover

Overview

JavaScript/TypeScript Playwright (this manual is Python-focused) Worth flagging early: a huge amount of Playwright's own official documentation and community content is written JS/TS-first (since that's Playwright's native language and where the built-in test runner lives). You'll frequently find yourself reading JS examples online and needing to mentally translate syntax to Python (e.g., page.click() stays similar, but async/await patterns, config files, and the test runner itself differ). This manual won't teach you that translation — it sticks to Python + Mobile native app testing (Appium territory) Mobile web emulation (Chapter 2, above) is in scope — testing a website as it renders in a mobile browser. Testing an actual native iOS/Android app (a compiled app installed from an app store) is a fundamentally different problem requiring Appium, which automates the OS-level app itself rather than a browser. Don't confuse the two when scoping out future learning — they're different tools solving different problems. Load/performance testing (that's k6/JMeter/Locust) Playwright automates one browser session behaving like one real user — it's not built to simulate thousands of concurrent users hitting a server to measure throughput/latency under load. That's a separate discipline (performance/load testing) with its own dedicated tools: k6 (modern, scriptable, popular in CI pipelines), JMeter (older, GUI-heavy, still widely used in enterprises), and Locust (Python-based, code-first). If load testing comes up in your Bizlevate work, it'd be a separate learning track from this one. Got it — same exhaustive depth for every part going forward, and when we hit API testing (Part 4, Ch. 18) I'll break down GET/POST/PUT/DELETE with real detail then too. Moving on to Part

pytest-playwright throughout.