lecture 1 of 180 completed

Where auto-waiting stops helping

Playwright waits for you almost everywhere. Knowing the few places it cannot help is what separates a junior from a mid-level engineer.

What you'll learn

  • Where Playwright's auto-waiting helps and where it stops
  • Why moving a value out of expect breaks retrying
  • The most common mistake made by people new to Playwright

In your first weeks with Playwright you will think waiting is a solved problem. Most of the time it is. Then you hit a test that fails once a week and nobody can explain it.

Let's understand exactly what Playwright waits for, so you know when you are on your own.

Before every action, Playwright runs actionability checks. That means it waits until the element is attached to the page, visible, stable (not moving), and enabled. Only then does it click.

full course

Keep reading with the full course

The Foundations track and the first lessons in each framework are free. This lesson needs full course access. A course plan includes all lessons for Playwright, Cypress and Selenium.

See course plans →