Exit course
Chapter 10 of 10 Beginner 6 min read Updated

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?

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 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?

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?

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?

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?

${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?

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?

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?

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?

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.

Where to go next#

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.