lecture 12 of 220 completed

Implicit waits, and why you should not use them

Every legacy suite has them. You need to recognise them, understand the bug they cause, and know what to write instead.

What you'll learn

  • What an implicit wait does, and why it waits for the wrong thing
  • Why mixing implicit and explicit waits causes strange timing bugs
  • What to write instead

You will meet implicit waits in the first Selenium codebase you join, and you need to understand them well enough to remove them safely.

What they are. One setting that tells the driver: whenever an element is not found, keep retrying for up to this long before giving up.

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 →