Playwright Cheat Sheet

By Syncfusion®, Inc. · Last updated November 13, 2026

A one-page reference for the whole course: CLI commands, test structure, locators, actions, assertions, configuration, fixtures, authentication, network mocking, API testing, debugging, reporting and CI, with runnable examples and three review exercises.

What you will learn

• Find the right Playwright command or API quickly
• Recall the best-practice choice for locators, waits and assertions
• Combine UI, network and API features in one test

Playwright Cheat Sheet

• This page collects the most used commands and APIs from the whole course, in one place.
• Each section has a short table and a box you can run. The lesson that teaches it in depth is named at the start.
• Keep it open while you write tests.

Simple lesson: look things up here. Learn them in the lesson named next to each section.

A Real-World Example

• One test can use almost everything from this course: a logged-in user, a mocked API, locators, actions and web-first assertions.

What You Will Find

1. CLI commands and test structure.
2. Locators and actions.
3. Assertions.
4. Configuration and fixtures.
5. Authentication, network and API.
6. Debugging, reporting and CI.

Commands and Structure

CLI Commands

Test Structure

Simple lesson: npx playwright test with flags runs anything. test, describe, hooks and steps shape a file.

Locators and Actions

Locators (best first)

Actions

Simple lesson: prefer roles, labels and test ids. Filter and chain to reach one element.

Assertions

Web-First Assertions (they retry)

• Always await them. Plain value checks (toBe, toEqual, toContain) do not retry.
• expect.soft() keeps going after a failure. expect.poll() and toPass() retry your own code.

Configuration and Fixtures

Config Options You Will Use

Fixtures

export const test = base.extend<{ cartPage: CartPage }>({
  cartPage: async ({ page }, use) => {
    const cartPage = new CartPage(page); // setup
    await use(cartPage);                // the test runs here
    // teardown goes after use()
  },
});

• Built-in fixtures: page, context, browser, request, browserName, baseURL.
• { scope: 'worker' } shares one value per worker. { auto: true } runs without being asked for.

Simple lesson: the config sets defaults for every test. Fixtures give each test what it needs.

Authentication, Network and API

Authentication

Network

API

Simple lesson: storage state for logins, page.route for mocks, request for the API.

Debugging, Reporting and CI

Simple lesson: the trace answers most questions. Reports and CI share the answers with your team.

TL;DR

• CLI: npx playwright test plus flags. show-report and show-trace open results.
• Locators: roles, labels and test ids first. Filter and chain.
• Assertions: await expect(locator)... retries. Plain expect does not.
• Config and fixtures set up every test. Storage state logs in once.
• page.route mocks, request calls the API, traces explain failures.
• CI: install, test, upload. Shard for speed.

Common mistakes

Check Yourself

Exercises

What to Remember

• This page is a map. The named lessons are the territory.
• Roles and labels, web-first assertions, no fixed waits.
• Log in once, mock what is rare, test the API directly.
• Traces, reports and CI turn failures into fixes.
• You now know Playwright from the first test to AI agents. Keep practising on real projects.