lecture 8 of 170 completed

Projects as an architectural tool

Projects are not just a browser list. Dependencies, teardown and option fixtures make them the main structural feature of the config.

What you'll learn

  • How projects express dependencies and ordering
  • How option fixtures turn projects into roles and environments
  • Why the matrix multiplies faster than teams expect

Most teams use projects for one thing: a list of browsers. That is the smallest use of the most structurally powerful feature in Playwright's config, and knowing the rest is a clear senior marker.

A project is a named configuration that runs a set of tests. What varies between projects is up to you: browser, device, environment, role, test directory, or your own option fixtures.

Use one: dependencies and ordering.

members only

Keep reading with the full course

The Foundations track and the first 5 lectures of each framework are free. This lecture is part of the paid course, which unlocks every lecture, all three frameworks, and downloads.

See the options →