---
title: 'Knowledge check | Selenium IDE: Codeless Test Automation'
description: Ten questions on the decisions that matter most when you build and run
  Selenium IDE tests. Each answer comes with a short explanation, so a wrong answer…
source_url:
  html: https://testingbot.com/resources/courses/selenium-ide/knowledge-check
  md: https://testingbot.com/resources/courses/selenium-ide/knowledge-check.md
---

Course

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

Chapter 10 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 10 of 10 Beginner 6 min read Updated Nov 2026 

# Knowledge check

Ten questions on the decisions that matter most when you build and run Selenium IDE tests. Each answer comes with a short explanation, so a wrong answer points you back to the right chapter.

1. A colleague wants to install Selenium IDE from the Chrome Web Store, following a 2021 tutorial. What do you tell them?

 That is still the official way; the desktop app is only for Linux The extension was version 3 and no longer runs in current Chrome; install the version 4 desktop app from the GitHub releases page or with `npm install -g selenium-ide` Selenium IDE was discontinued; there is no way to run it any more

Version 4 is an Electron desktop app for Windows, macOS and Linux, with new 4.1.0 betas released in November 2026. The extension era ended when Chrome moved to Manifest V3.

2. A step's target is `css=.btn-blue` and its stored `targets` also contain `id=checkout`. After a restyle the class is gone. What happens when the test runs?

 The IDE silently switches to `id=checkout` and the step passes The step passes in the IDE but fails in `selenium-side-runner` The step fails in both, because version 4 only plays the selected target; you switch it to `id=checkout` yourself

The fallback loop is commented out in the shared runtime, so the stored alternatives are a menu, not a safety net. Choosing a stable target up front is what prevents this.

3. After a click that loads a new page, `assertText | css=h1 | Dashboard` sometimes fails with a stale element error. Both pages have an `h1`. What is the best fix?

 Before the `assertText`, wait for something only the new page has, or use `waitForText | css=h1 | Dashboard` Add `pause | 2000` after the click Change `assertText` to `verifyText`

`assertText` waits for an `h1` to exist, and the old page's one does. Waiting for a new-page-only element, or for the text itself, removes the race; a pause only makes it rarer, and `verify` only changes what happens after the failure.

4. A test has five `verifyText` checks followed by a step that marks the session passed on TestingBot. The second check fails. What does the dashboard show?

 Failed, because a failed verify stops the test No result, because the runner never reached the last step Failed, because TestingBot reads the runner's exit code Passed, because commands after a failed verify still run, including the reporting step

`verify` records the failure and continues. The runner still reports the test as failed locally, but the reporting step ran. Use `assert` for the checks that decide the result in tests that report it themselves.

5. Which condition is true when the variable `status` holds `Active`?

 `if | "${status}" === "Active"` `if | ${status} === "Active"` `if | status === "Active"`

In conditions and `executeScript`, variables are passed as script arguments: `${status}` becomes `arguments[0]`. Quoted, it becomes the literal text `arguments[0]`; without `${}` it is an undefined JavaScript name.

6. You want a step to run on the grid but never when someone plays the test in the IDE. How?

 Put the step in a suite with Persist Session Disable the step; the runner plays disabled steps Wrap it in `if | ${env:ON_GRID} === "yes"` and set `ON_GRID=yes` only in the shell that starts the runner

`${env:NAME}` reads the environment of the process that plays the test. It is not set in the IDE, so the condition is false there. Disabled steps are skipped by the runner too.

7. A shared test `Log in` uses `${username}` and `${password}`. Where should it live?

 In the project, outside every suite, called with `run` after the caller stores both variables As the first test of every suite, so the variables are set for the rest In a separate `.side` file that the other projects call

On its own it would type the literal text `${username}`, so it must not run as a test. The runner skips tests that are in no suite, and `run` cannot reach into another project file.

8. You start `selenium-side-runner -w 6` on a suite marked Parallel, against a grid plan with two parallel sessions. Several tests fail with "Driver took too long to build". Why?

 Six workers need six local browsers as well Four sessions wait in the grid's queue, and the runner gives up on a session that has not started within 30 seconds `-w` is ignored for Parallel suites

The runtime has a fixed 30-second limit for starting a browser. Queued sessions exceed it. Keep `-w` at or below the parallel sessions your plan allows.

9. A CI job should fail when any recorded test fails. What does it need to check?

 That the JSON report from `-o` exists That no screenshot was written by `-z` The word "PASS" in the output Nothing special: the runner exits with a non-zero code when a test fails, and the CI step fails on it

The exit code is 0 only when every test passed. Reports and screenshots are for people; the exit code is for the CI system.

10. You exported a suite to Python. Which statement is accurate?

 The export behaves exactly like the IDE, including its waiting The export runs on any grid, because it reads the runner's `--server` option It is a readable draft: waiting after actions, `${env:...}` variables and some commands are lost, and it hard-codes a local Chrome

In our run all eight exported tests failed before editing. Use the export to see which WebDriver calls your steps map to, then rewrite it with explicit waits and fixtures.

Check answers

## Where to go next[#](https://testingbot.com#where-to-go-next)

- Write the same tests in code: [Selenium with Python and pytest](https://testingbot.com/resources/courses/selenium-python) or [Selenium with TestNG](https://testingbot.com/resources/courses/selenium-testng).
- Give a growing suite structure: [Page Object Model](https://testingbot.com/resources/courses/page-object-model).
- Make tests reliable: [Flaky Tests](https://testingbot.com/resources/courses/flaky-tests).
- Earn the [TestingBot Selenium IDE certification](https://testingbot.com/resources/courses/selenium-ide/certification): pass the exam and run your suite on TestingBot under the build name `certificate-selenium-ide`.

[Previous · Chapter 9 Export Selenium IDE Tests to Code, and When to Graduate](https://testingbot.com/resources/courses/selenium-ide/export-to-code)
## You finished Selenium IDE: Codeless Test Automation

Put what you learned into practice. Run your tests on 6100+ real browsers and physical iOS and Android devices.

[Start free trial](https://testingbot.com/users/sign_up) [See pricing](https://testingbot.com/pricing) [Browse other courses](https://testingbot.com/resources/courses)

## TestingBot Selenium IDE Certification

Turn this course into a free, resume-worthy credential: pass the exam, run the course suite on TestingBot, and get a verifiable certificate for your LinkedIn profile.

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