The Selenium Suite
| Component | What it is | When to use |
|---|---|---|
| Selenium WebDriver | The main library with browser control commands | Almost all automation work |
| Selenium Grid | Runs tests on many machines and browsers at the same time | Large suites and cross-browser testing |
| Selenium IDE | Browser extension that records and plays back actions | Quick demos and learning |
| Selenium Manager | Built-in helper that downloads the right browser driver for you | Automatic (you do not call it yourself) |
How a Command Travels
When your code says driver.get("https://example.com"), several things happen:
| Part | Role |
|---|---|
| Client library | The selenium package you install. Gives you driver.find_element, click and so on |
| Browser driver | A small program made by the browser vendor that receives commands |
| Browser | Does the real work: loads pages, runs JavaScript |
| W3C WebDriver protocol | The official standard language between client and driver, so all browsers behave similarly |
Browser Drivers and Selenium Manager
Every browser needs its own driver: chromedriver for Chrome, geckodriver for Firefox, msedgedriver for Edge. In the past you had to download the exact matching version by hand, and tests broke every time the browser updated.
Selenium 4 Highlights
- Fully W3C compliant (more stable across browsers)
- Relative locators: find an element by its position, for example to the left of another one
- New windows and tabs created with
switch_to.new_window - Better
ActionsAPI for mouse and keyboard - Chrome DevTools and BiDi (two-way) support for network and console information
- Improved Grid 4 with Docker and observability support
Grid in One Picture
You will build and use a Grid later in the course.
Conclusion
Your script uses the Selenium library to send W3C WebDriver commands to a browser driver, which controls the browser. Selenium Manager removes the old pain of downloading drivers.

