Workshop

Twenty blocks. Three parts. One day of Playwright.

Before you arrive
  1. 00.

    Install Playwright and land one green test so day-of goes smoothly.

Basics

Install, debug, run.
  1. 01.

    Record your first tests using codegen

  2. 02.

    Break things, debug them and analyze with the trace viewer.

  3. 03.

    Basic configuration options for your Playwright setup.

  4. 04.

    Learn how to give your test suite some structure.

Writing tests

The craft of real tests.
  1. 01.

    Understand Playwright's actionability and locators.

  2. 02.

    Learn how to add assertions and avoid all these "waitFor"s.

  3. 03.

    Use accessibility-aware matchers to lock down structure and catch a11y regressions with clear failure messages.

  4. 04.

    Read data out of the page so you can assert on values you don't know up front.

  5. 05.

    Learn how to implement a setup step and reuse browser state.

  6. 06.

    Recognize the patterns behind flaky tests and apply the right tool for each.

  7. 07.

    Learn how to take some pictures and implement visual regression tests.

  8. 08.

    Block, mock, and modify network requests so tests stay fast and deterministic.

  9. 09.

    Use the `request` fixture to hit HTTP endpoints directly — no browser, no DOM.

  10. 10.

    Subscribe to dialogs, console messages, errors, downloads, and new tabs.

  11. 11.

    Stitch the workshop's patterns into one end-to-end purchase against the local /checkout.

AI

Playwright in the agentic era.
  1. 01.

    See why a coding agent reaches for `@playwright/cli` over MCP, and run your first agent-driven browser session.

  2. 02.

    Have your coding agent turn a CLI-driven session into a runnable Playwright spec — and understand exactly what it's doing under the hood.

  3. 03.

    Lift repeated locators into a Page Object Model with the agent doing the typing — and decide which methods earn their keep.

  4. 04.

    Lift repeated setup into a Playwright fixture with the agent doing the typing — and decide what should and shouldn't be hidden.

  5. 05.

    Spot the test-authoring tasks where AI is the obvious tool — pattern-following, typing-heavy work where the agent does the labour and you do the deciding.