Selenium Documentation

What it is

Selenium is an open source umbrella project for browser automation, and WebDriver is its core: a language binding that drives Chrome, Firefox, Edge or Safari through each browser's driver using the W3C WebDriver protocol. The official documentation is the reference for how Selenium works today, maintained by the project itself.

What it covers

• WebDriver: getting started, browser options, finding elements, interacting with them, waits, the Actions API for keyboard and mouse, frames, windows and alerts.
• Selenium Manager: the tool built into Selenium 4 that locates or downloads the right driver and browser automatically, so you no longer manage drivers by hand.
• Grid: running sessions on remote machines or containers, in parallel and across browsers.
• IDE: the record and playback browser extension.
• Test practices: the project's own guidance on page object models, domain-specific languages, test independence and practices to avoid.

Examples are provided side by side in Java, Python, C#, Ruby, JavaScript and Kotlin, so you can read them in the language your team uses.

Is it worth your time?

If you are learning Selenium, this should be your main reference. Many blog tutorials are written for Selenium 3 and still show manual driver downloads, system properties and implicit waits used everywhere; the official pages show the current way. The waits page and the test practices section are especially worth reading closely, because synchronisation and structure cause most Selenium pain.

Prerequisites

Basic programming in one supported language. For Java, be comfortable with classes, methods and a build tool such as Maven before you start, and pair the docs with a test framework such as TestNG or JUnit 5.

Free or paid?

Selenium and its documentation are free and open source under the Apache 2.0 licence. Commercial cloud grids exist, but you do not need them to learn or to run Selenium on your own machine or in Docker.

What you can do after

Write reliable browser tests with stable locators and explicit waits, structure them with page objects, capture evidence on failure, and run them in parallel on Selenium Grid in CI.

Common questions

Selenium or Playwright? Both are widely used. Selenium is especially common in Java teams and large enterprises with existing suites; Playwright is popular for new TypeScript projects. Check job postings in your market.

Do I still need to download ChromeDriver? Not with Selenium 4: Selenium Manager handles it by default.