---
title: Install Selenium IDE and Record Your First Test | TestingBot
description: In this chapter you install the Selenium IDE desktop app, record a login
  on a practice site, add one check, play it back and look at the file it saves. By…
source_url:
  html: https://testingbot.com/resources/courses/selenium-ide/install-and-record-your-first-test
  md: https://testingbot.com/resources/courses/selenium-ide/install-and-record-your-first-test.md
---

Course

[Selenium IDE: Codeless Test Automation](https://testingbot.com/resources/courses/selenium-ide)

Chapter 2 of 10

1. [1 Selenium IDE Tutorial: Codeless Test Automation](https://testingbot.com/resources/courses/selenium-ide)
2. [2 Install Selenium IDE and Record Your First Test](https://testingbot.com/resources/courses/selenium-ide/install-and-record-your-first-test)
3. [3 Commands, Targets and Locators in Selenium IDE](https://testingbot.com/resources/courses/selenium-ide/commands-targets-and-locators)
4. [4 Assertions, Verifications and Waits in Selenium IDE](https://testingbot.com/resources/courses/selenium-ide/assertions-verifications-and-waits)
5. [5 Variables, store and Control Flow in Selenium IDE](https://testingbot.com/resources/courses/selenium-ide/variables-and-control-flow)
6. [6 Reusing Tests and Organising Suites in Selenium IDE](https://testingbot.com/resources/courses/selenium-ide/reusing-tests-and-suites)
7. [7 Run .side Files with selenium-side-runner](https://testingbot.com/resources/courses/selenium-ide/run-side-files-with-selenium-side-runner)
8. [8 Run Selenium IDE Tests on the TestingBot Grid](https://testingbot.com/resources/courses/selenium-ide/run-on-testingbot)
9. [9 Export Selenium IDE Tests to Code, and When to Graduate](https://testingbot.com/resources/courses/selenium-ide/export-to-code)
10. [10 Knowledge check](https://testingbot.com/resources/courses/selenium-ide/knowledge-check)

[Exit course](https://testingbot.com/resources/courses)

 Chapter 2 of 10 Beginner 8 min read 2 quick checks Updated Nov 2026 

# Install Selenium IDE and Record Your First Test
On this page
1. [Install the app](https://testingbot.com#install-the-app)
2. [Create a project](https://testingbot.com#create-a-project)
3. [Record a login](https://testingbot.com#record-a-login)
4. [Add a check](https://testingbot.com#add-a-check)
5. [Play it back](https://testingbot.com#play-it-back)
6. [What is inside a .side file](https://testingbot.com#what-is-inside-a-side-file)
7. [The practice project](https://testingbot.com#the-practice-project)

In this chapter you install the Selenium IDE desktop app, record a login on a practice site, add one check, play it back and look at the file it saves. By the end you have a `.side` project that the rest of the course builds on.

## Install the app[#](https://testingbot.com#install-the-app)

Selenium IDE 4 is a desktop application. Pick one of the two ways the project offers:

- **Download a build** from the [releases page](https://github.com/SeleniumHQ/selenium-ide/releases): a `.dmg` or `.zip` for macOS, a `Setup .exe` for Windows, an `.AppImage` for Linux. Version 4.1.0-beta.3 (6 November 2026) is the newest at the time of writing.
- **Install it with npm** if you have Node.js: `npm install -g selenium-ide`, then start it with `selenium-ide`. This installs the newest release, betas included.

The builds are not code-signed yet. On macOS the first launch says Apple could not verify the app; allow it under **System Settings \> Privacy & Security \> Open Anyway**. On Windows, SmartScreen shows "Windows protected your PC"; click **More info** and then **Run anyway**. Do this only for a file you downloaded from the official releases page.

If you find an old guide that tells you to add Selenium IDE from the Chrome Web Store, that is version 3, which no longer runs in current Chrome (see the [introduction](https://testingbot.com/resources/courses/selenium-ide)).

## Create a project[#](https://testingbot.com#create-a-project)

When the IDE starts it offers **Create Project** and **Load Project**. Create one. A project is everything that ends up in one `.side` file: a name, a **base URL** , a list of tests and a list of suites. The new project already contains one empty test and one suite.

Set the project's base URL to `https://the-internet.herokuapp.com`. Commands such as `open | /login` are resolved against it, which is what lets you point the same tests at a staging server later without editing every step.

## Record a login[#](https://testingbot.com#record-a-login)

The flow to record: open the login page, type a username and password, click **Login**.

1. Select the test in the **Tests** tab and rename it to `Log in with valid credentials`.
2. Press **Record**. The IDE opens the page in its playback window, the area labelled "This is where recording and playback will occur".
3. Go to `/login`, click the **Username** field and type `tomsmith`, click **Password** and type `SuperSecretPassword!`, then click **Login**.
4. Press **Stop**.

The test now has a list of commands. Each row has three columns: the **command** , its **target** (usually the element) and a **value** (the text to type, a variable name, an expected value):

| Command | Target | Value |
| --- | --- | --- |
| `open` | `/login` | |
| `type` | `id=username` | `tomsmith` |
| `type` | `id=password` | `SuperSecretPassword!` |
| `click` | `css=.radius` | |

Recordings are rarely this clean. You will often see extra `click` rows for every field you clicked into, a `setWindowSize` row and sometimes a `mouseOver`. Delete what the test does not need: fewer steps means fewer things that can break. Right-click a row for **Delete Command** , **Disable Command** , **Play This Step** and **Record From Here**.

## Add a check[#](https://testingbot.com#add-a-check)

A test without a check only proves that the steps did not crash. Add two commands after the click: select the last row, use **Add Command** (or right-click and **Insert Command** ) and fill in the fields.

| Command | Target | Value |
| --- | --- | --- |
| `assertElementPresent` | `css=#flash.success` | |
| `assertText` | `css=h2` | `Secure Area` |

The first waits until the green "You logged into a secure area!" banner exists; the second checks the page heading. The order matters, and chapter 3 explains why: in our runs, putting `assertText` first made the test fail now and then.

Your recorded test types the credentials and clicks Login, and it passes every time. What does that prove?

 That a user can log in That the login page has no bugs Only that the fields and the button could be found and used; nothing checked where the click led

Without an assertion, a login that shows "Your password is invalid!" passes too. Add a check on something only a logged-in user sees, such as the success banner or the Secure Area heading.

## Play it back[#](https://testingbot.com#play-it-back)

Press **Play**. The IDE runs each command in order and marks it green when it passed or red when it failed, with the error underneath. Two project settings under **Config \> Project** are worth knowing now:

- **Step Timeout** : how long a step may take, including waiting for its element, before it fails.
- **Step Delay** : a pause before each step. Leave it at zero for real runs; raise it only to watch what happens.

Save with **File \> Save Project**. You get one file, for example `the-internet.side`.

## What is inside a .side file[#](https://testingbot.com#what-is-inside-a-side-file)

A `.side` file is JSON. Here is a complete project with the test you just recorded, trimmed to the fields that matter. You can save it as `first-test.side` and open it with **Load Project** , or run it from the command line in chapter 6. We ran exactly this file with `selenium-side-runner` in Chrome and Firefox:

```json
{
  "id": "first-project",
  "version": "3.0",
  "name": "first-project",
  "url": "https://the-internet.herokuapp.com",
  "urls": ["https://the-internet.herokuapp.com/"],
  "plugins": [],
  "suites": [{
    "id": "suite-smoke",
    "name": "Smoke",
    "persistSession": false,
    "parallel": false,
    "timeout": 30000,
    "tests": ["test-login"]
  }],
  "tests": [{
    "id": "test-login",
    "name": "Log in with valid credentials",
    "commands": [
      { "id": "c1", "command": "open", "target": "/login", "value": "" },
      { "id": "c2", "command": "type", "target": "id=username", "value": "tomsmith",
        "targets": [["id=username", "id"], ["name=username", "name"], ["css=#username", "css:finder"]] },
      { "id": "c3", "command": "type", "target": "id=password", "value": "SuperSecretPassword!" },
      { "id": "c4", "command": "click", "target": "css=.radius", "value": "" },
      { "id": "c5", "command": "assertElementPresent", "target": "css=#flash.success", "value": "" },
      { "id": "c6", "command": "assertText", "target": "css=h2", "value": "Secure Area" }
    ]
  }]
}
```

What to notice:

- **`url`** is the base URL. The `open` command only stores `/login`.
- **`version: "3.0"`** is the file format version that IDE 4 writes for a new project; it is not the IDE's version. Files from IDE 3 carry `"2.0"`, and some of their commands were renamed in version 4 (`storeXpathCount` became `storeElementCount`, for example). The project's `@seleniumhq/side-migrate` package converts old files.
- **Tests and suites are separate lists.** A suite refers to its tests by `id`, so one test can be part of several suites.
- **`targets`** holds the other locators the recorder found for the same element (chapter 2). The IDE fills it in; the hand-trimmed commands above have it on one row only.
- **Passwords are stored in plain text.** Anyone who can read the file can read them. Use a test account that has no access to anything real, and never record your own credentials.

The IDE writes long random ids (UUIDs). The short ones above work just as well; they only have to be unique within the file.

You want to run the same recorded tests against `https://staging.example.com` instead of production. What should the recording look like so that this is easy?

 `open` commands with paths such as `/login`, and the host only in the project's base URL `open` commands with full URLs, so each step is explicit One copy of the project per environment

Relative paths are resolved against the base URL, which you can change in one place or override with `--base-url` on the command line. Absolute URLs ignore the base URL, so every one of them would need editing.

## The practice project[#](https://testingbot.com#the-practice-project)

The rest of the course uses one project, `the-internet.side`, with eight tests in two suites:

| Suite | Test | Page |
| --- | --- | --- |
| Smoke | Log in with valid credentials | `/login` |
| Smoke | Wrong password shows an error | `/login` |
| Smoke | Check both checkboxes | `/checkboxes` |
| Smoke | Pick an option from the dropdown | `/dropdown` |
| Smoke | Wait for content that loads later | `/dynamic_loading/2` |
| Smoke | Log in and log out | `/login`, reuses a "Log in" test |
| Variables and control flow | Store and reuse values | `/login` |
| Variables and control flow | Add and remove elements | `/add_remove_elements/` |

Each chapter shows the commands of the tests it introduces. Record them yourself or type them in with **Add Command** : typing commands is a normal way to work in the IDE, not a workaround.

[Previous · Chapter 1 Selenium IDE Tutorial: Codeless Test Automation](https://testingbot.com/resources/courses/selenium-ide) [Next · Chapter 3 Commands, Targets and Locators in Selenium IDE](https://testingbot.com/resources/courses/selenium-ide/commands-targets-and-locators)

On this page

1. [Install the app](https://testingbot.com#install-the-app)
2. [Create a project](https://testingbot.com#create-a-project)
3. [Record a login](https://testingbot.com#record-a-login)
4. [Add a check](https://testingbot.com#add-a-check)
5. [Play it back](https://testingbot.com#play-it-back)
6. [What is inside a .side file](https://testingbot.com#what-is-inside-a-side-file)
7. [The practice project](https://testingbot.com#the-practice-project)

Certification

Earn the free, resume-worthy TestingBot Selenium IDE Certification for this course.

[How it works](https://testingbot.com/resources/courses/selenium-ide/certification)
