lecture 11 of 220 completed

How Selenium actually runs

A driver process controlling the browser. Why Selenium makes you do the waiting and asserting.

What you'll learn

  • How a driver process sits between your code and the browser
  • Why Selenium makes you handle waiting yourself
  • Why you start and stop the browser explicitly

Selenium is the oldest of the three big tools, and it does the least for you. That sounds like bad news. It is actually why Selenium questions come up so often in interviews: nothing is hidden, so your answers show whether you really understand testing.

Here is the model. Your test is a program (here, Node.js) that talks to a driver. The driver controls a real browser. Every command, like find this element or click it, is a message sent to the driver.

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 →