Pathwise

Manuals / Playwright with Python / Chapter 1

Part 0 · Background · beginner · Day 1 · Chapter 1 of 61

0. What is Playwright, Really

History — built by Microsoft, evolved from the Puppeteer team Playwright's origin story matters more than it seems on the surface. The core engineers who built Playwright — most notably Andrey Lushnikov, Pavel Feldman, and Boris Yankov — were previously on the team at Google that built and maintained Puppeteer, the Node.js library for controlling headless Chrome.

Path progress
1%

Step 1 of 3

History — built by Microsoft, evolved from the Puppeteer team

Playwright's origin story matters more than it seems on the surface. The core engineers who built Playwright — most notably Andrey Lushnikov, Pavel Feldman, and Boris Yankov — were previously on the team at Google that built and maintained Puppeteer, the Node.js library for controlling headless Chrome. When they moved to Microsoft, they took everything they'd learned from Puppeteer's limitations and built something new instead of iterating on the old codebase. This "second attempt by the same people" origin is why Playwright feels less like a patched-together tool and more like a deliberately designed one. Puppeteer was built specifically for Chrome/Chromium via the Chrome DevTools Protocol (CDP). Its creators knew intimately where that architecture broke down — mainly, it couldn't reliably control Firefox or Safari/WebKit. Playwright was designed from day one to solve that: a single API surface that talks to all three major browser engines. First released publicly in January 2020, Playwright is comparatively young next to Selenium (which dates back to 2004). That youth is actually a selling point in interviews — it means the tool was designed with full knowledge of modern web apps (SPAs, shadow DOM, complex async behavior) rather than retrofitted onto assumptions from the mid-2000s web.

History — built by Microsoft, evolved from the Puppeteer teamDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →Page under testdrag · tap →Automation pathdrag · tap →Multi-browserdrag · tap →
DocsRepoArticle

Quick check

Playwright’s core engineers previously built which tool?

Do this now

Write one sentence: “Playwright exists because ___.”

Was this step clear?
Chapter learning outcomes
  • History — built by Microsoft, evolved from the Puppeteer team
  • Open-source, actively maintained, backed by Microsoft
  • Why it was created (gaps in Selenium/Puppeteer)

Clear these before you leave

Side quest

0. What is Playwright, Really deliverable

Apply one idea from “History — built by Microsoft, evolved from the Puppeteer team” in a small script or note.