Skip to main content

Selenium IDE

Selenium IDE records your interactions with a website and plays them back as a browser test. Tests are saved as a .side project file, which you can run on TestingBot with the selenium-side-runner command line tool or upload to TestingBot's Codeless Automation.

Installing Selenium IDE

Selenium IDE 4 is a desktop application for Windows, macOS and Linux. As of November 2026 the newest release is 4.1.0-beta.3 (published 6 November 2026). You can install it in two ways:

  • Download the installer for your operating system from the GitHub releases page.
  • Or, with Node.js installed, run npm install -g selenium-ide and start it with selenium-ide.

The builds are not code-signed yet, so macOS and Windows warn you the first time you open the app. The Selenium IDE README explains how to allow it.

Older guides describe Selenium IDE as a Chrome or Firefox add-on. That was version 3: the Chrome extension stopped working when Chrome disabled Manifest V2 extensions (see selenium-ide#1882), and the last Firefox add-on release, 3.17.4, dates from February 2022. Use the desktop app for new tests; .side files recorded with version 3 can still be opened.

What can Selenium IDE do for me?

Here's one example: you can record yourself clicking through various pages on your website.
During this recording, you can right click various elements and indicate that these need to be present, or contain a specific value.

Once you've finished this recording, you can choose to instantly playback the recording.
The IDE will mimic your recorded behavior together with the assertions you've recorded.

TestingBot integration with Selenium IDE

When you finished recording a test, save the project from Selenium IDE.
The saved file (with a .side extension) can be uploaded into TestingBot's Codeless Automation.

There, you can indicate on which browsers and platforms the test needs to run.
You can schedule tests and indicate if you would like to be alerted when a test fails.

Advanced: Selenium SIDE runner with TestingBot

You can run .side files from the command line, for example in CI, with selenium-side-runner. As of November 2026 the version npm installs is 4.1.0-beta.3, which needs Node.js 22 or newer. You do not need to install browser drivers to run on TestingBot.

npm install -g selenium-side-runner
selenium-side-runner --version

Describe the TestingBot hub and the browser and platform in a .side.yml file next to your project. The runner loads it automatically from the current folder:

server: "https://your-key:your-secret@hub.testingbot.com/wd/hub"
capabilities:
  browserName: chrome
  browserVersion: latest
  platformName: WIN11
  "tb:options":
    build: my-selenium-ide-build
maxWorkers: 1

Keep the secret out of the command line and out of git. Anything passed as --server is visible in the process list (ps) and often in CI logs, so put the hub URL in .side.yml instead. The runner does not expand environment variables in this file, so treat it as a secret: add it to .gitignore, make it readable only by you (chmod 600 .side.yml), and in CI write it from your CI system's secret store at the start of the job, as shown below. Keep the .side project itself free of credentials.

# CI: TB_KEY and TB_SECRET come from the CI secret store
umask 077
cat > .side.yml <<EOF
server: "https://${TB_KEY}:${TB_SECRET}@hub.testingbot.com/wd/hub"
capabilities:
  browserName: chrome
  browserVersion: latest
  platformName: WIN11
maxWorkers: 1
EOF

Then run the project. Options on the command line are merged over .side.yml, so -c can switch the browser while keeping the rest:

selenium-side-runner project.side
selenium-side-runner -c "browserName=firefox" project.side

You can also pass capabilities inline: -c "browserName=chrome browserVersion=latest platformName=WIN11". The capabilities generator lists every browser and platform combination, and test options lists what else tb:options accepts.

The runner starts one TestingBot session per test and exits with code 1 when a test fails, so a CI step fails the build on a failing test.

Mark tests as passed

selenium-side-runner does not report results to the grid, so by default every session shows up in the TestingBot dashboard without a passed/failed status. A test can report its own result with an executeScript command (see annotating tests): TestingBot intercepts tb:test-result=passed and tb:test-name=... instead of running them in the browser.

These commands are not valid JavaScript, so in the IDE or a local browser the step would fail. Add them as the last steps of each test, inside an if block on an environment variable that is only set for TestingBot runs:

Command Target
if ${env:TB_REPORT} === "yes"
executeScript tb:test-name=Log in with valid credentials
executeScript tb:test-result=passed
end
export TB_REPORT=yes
selenium-side-runner project.side

Because the block is the last step, only tests that reach the end are marked as passed. A failed assert stops the test before the block, so that session gets no status (not "failed"); the runner's output and exit code still show the failure. A failed verify does not stop the test, so use assert commands for checks that decide the result.

Parallel sessions and queueing

selenium-side-runner gives up on a browser session that has not started within 30 seconds (Driver took too long to build), and this limit cannot be changed. A session that waits in TestingBot's queue for a free slot can take longer than that; the grid then still starts it, and it sits idle without a name until it times out.

  • Keep maxWorkers (or -w) at or below the number of parallel sessions your plan allows.
  • Run one browser after another rather than several runner processes at the same time.
  • Avoid --retries right after a "Driver took too long to build" error: the retries join the same queue.
Was this page helpful?
Last updated