Selenium IDE Tutorial: Codeless Test Automation
A free Selenium IDE tutorial: record a test, pick stable locators, assert and wait, use variables and if/while/times, reuse tests, run .side files with selenium-side-runner on a cloud grid, and export to code.
What you will learn
- Selenium IDE Tutorial: Codeless Test Automation
- Install Selenium IDE and Record Your First Test
- Commands, Targets and Locators in Selenium IDE
- Assertions, Verifications and Waits in Selenium IDE
- Variables, store and Control Flow in Selenium IDE
- Reusing Tests and Organising Suites in Selenium IDE
- Run .side Files with selenium-side-runner
- Run Selenium IDE Tests on the TestingBot Grid
- Export Selenium IDE Tests to Code, and When to Graduate
- Knowledge check
On this page
Last reviewed 13 November 2026 against Selenium IDE 4.1.0-beta.3 and selenium-side-runner 4.1.0-beta.3 (both released 6 November 2026).
Selenium IDE records what you do in a browser and turns it into a test you can play back. You click, type and select; the IDE writes down each step as a command such as click, type or select, together with the element it acted on. Add a few checks, save, and you have an automated test without writing a line of code. That is what people mean by codeless test automation, and Selenium IDE is the open-source, free way to do it.
This course goes from that first recording to a small suite that runs from the command line on several browsers in the cloud, and it is honest about where recording stops being enough. Every test in it was built as a .side project file and run with selenium-side-runner, locally in Chrome and Firefox and on the TestingBot grid.
Selenium IDE in November 2026#
Most tutorials still describe Selenium IDE as a Chrome and Firefox extension. That is out of date, and it matters before you install anything:
- Version 3 was a browser extension. Chrome's switch to Manifest V3 extensions broke it in Chrome; the project's own issue tracker has the discussion (issue #1882, January 2025). The Firefox add-on is still listed on addons.mozilla.org, but its latest version, 3.17.4, dates from February 2022.
-
Version 4 is a desktop application (built on Electron) for Windows, macOS and Linux. You download it from the GitHub releases page or install it with
npm install -g selenium-ide. It records and plays back in its own built-in Chromium window by default. - It is maintained again. The previous release of the app was 4.0.1-beta.14 in July 2024. After more than two years without one, version 4.1.0 betas started shipping in November 2026 (beta.1 on 3 November, beta.3 on 6 November), with Electron, selenium-webdriver and the code exporters updated. The releases are still labelled beta and the binaries are not code-signed, so macOS and Windows warn you the first time you open them; the README explains how to allow it.
-
The command-line runner is the npm package
selenium-side-runner. Version 4.1.0-beta.3 is the one npm installs by default (itslatesttag), and it needs Node.js 22 or newer.
The project's homepage at selenium.dev still shows Chrome and Firefox extension buttons and a 2019 copyright line, and it says the IDE tries alternative locators when the first one fails. Chapter 2 shows that the version 4 runner no longer does that. When a tutorial and the tool disagree, this course goes with what the tool did when we ran it.
What codeless automation is good for#
A recorded test is quick to make and easy to read. That makes Selenium IDE a good fit for:
- Smoke tests of the main paths: can a user log in, search, add to cart. A handful of these catch the "the site is down" class of bug.
-
Reproducing a bug: record the steps once, attach the
.sidefile to the bug report, and anyone can replay it. - People who do not write code: testers, product owners and support staff can build and maintain these tests.
- Learning Selenium: every IDE command maps to a WebDriver call, and the export feature (chapter 8) shows you the code.
Where it stops being enough#
Codeless does not mean free of maintenance, and some things are hard or impossible in a recording:
- Test data and setup. Creating a fresh user through an API, seeding a database or reading a CSV file is code territory.
- Reuse beyond a project. You can reuse one test inside another (chapter 5), but there are no functions with parameters, no imports and no shared library across projects.
-
Review and history. A
.sidefile is JSON. It diffs badly, and two people editing the same project will conflict. - Large suites. Past a few dozen tests, the lack of structure (page objects, helpers, fixtures) makes changes expensive.
The usual path is to start codeless, keep the smoke tests that work, and move the rest to code when these limits start to hurt. Chapter 8 covers that move.
How the course is organised#
| Chapter | You learn |
|---|---|
| 1. Install and record your first test | the version 4 app, recording a login, playing it back, the .side file |
| 2. Commands, targets and locators | command/target/value, which locator to keep, what the stored fallbacks really do |
| 3. Assertions, verifications and waits |
assert vs verify, the commands that wait and the ones that do not |
| 4. Variables and control flow |
store, ${}, executeScript, if, while and times
|
| 5. Reusing tests and suites | the run command, suites, parallel and persistent sessions |
| 6. Run .side files with selenium-side-runner | the CLI, .side.yml, --steps, filters, exit codes |
| 7. Run on the TestingBot grid | several browsers, a build name, passed and failed results |
| 8. Export to code and when to graduate | Python and Java exports, what they get wrong, where to go next |
| 9. Knowledge check | ten questions on the decisions the course made |
The examples run against the-internet.herokuapp.com, a public practice site with a login form, checkboxes, a dropdown and content that loads late. You can replay every test in this course without an account anywhere.
Prerequisites#
- A computer that can run the Selenium IDE desktop app (Windows, macOS or Linux).
- Node.js 22 or newer for chapters 6 and 7. You type a few commands in a terminal there; nothing else needs code.
- A free TestingBot trial for chapter 7, if you want to run the suite in the cloud.
The course and its knowledge check are free and need no account. The optional TestingBot certification asks for a passed exam and your suite running green on TestingBot. It is issued by TestingBot, not by the Selenium project.