lecture 11 of 160 completed

Cross-browser coverage and driver version governance

Selenium's core value is browser reach. Its recurring operational cost is keeping drivers and browsers aligned.

What you'll learn

  • Why browser updates break pipelines overnight
  • How to pin versions so upgrades are deliberate
  • Why branching on browser inside a test is a trap

Chrome updated overnight and the entire pipeline failed the next morning with a message about an unsupported version. Every test, every team. That is the recurring cost of Selenium's greatest strength.

Why this happens and nothing else has the problem. Cypress and Playwright download and pin their own browsers. Selenium drives the browsers on your machines, so browser versions move underneath you on someone else's release schedule.

Governance, in order of how much control they give you.

Pin browser versions in your infrastructure. With Docker Grid nodes, use tagged images (selenium/node-chrome:120.0) rather than latest. Now an upgrade is a deliberate change you make on a Tuesday morning, not a surprise on a Friday night. This is the single most valuable change most teams can make.

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 →