Chrome Extension for Selenium: Record Tests, Then Know When to Write Code

What is the Chrome extension for Selenium?

It is Selenium IDE, an official extension maintained by the Selenium project that records what you do in the browser and replays it as an automated test. The project site lists it on the Chrome Web Store (official listing), and its documentation lives at selenium.dev/selenium-ide.

We do not have a Selenium IDE profile in our directory, so we link its official pages instead. From our catalogue, Katalon Recorder is the closest record-and-replay alternative, with a caveat covered below. Later sections cover the extensions testers use around either tool: cookie editors, user agent switchers, window resizers and inspectors.

Two names cause confusion. Selenium IDE is the extension you click. Selenium WebDriver is the programming library that drives a browser from code, using a driver such as ChromeDriver. The extension is the gentle on-ramp; WebDriver is where most professional suites end up.

Selenium IDE

Browser extension. Record, edit and replay tests in a visual editor. Good for quick checks and learning.

Selenium WebDriver

Code library for Java, Python, JavaScript, C# and more. Good for large, versioned test suites.

ChromeDriver

The bridge that lets WebDriver control Chrome. Its documentation is on developer.chrome.com.

One more point: an extension cannot replace a driver for cross-browser or headless runs in a build server. That is the line between record and playback and real automation.

How do I install Selenium IDE and record a test?

Add it from the Chrome Web Store, open it from the toolbar, and press record. You can have a first test replaying in a few minutes.

1. Open the Selenium IDE listing linked from selenium.dev/selenium-ide (Chrome Web Store ID mooikfkahbdckldjjndioackbalphokd), then click Add to Chrome.
2. Click the puzzle-piece Extensions icon and pin Selenium IDE.
3. Click its icon. The welcome dialog offers Record a new test in a new project, Open an existing project, Create a new project and Close the IDE; choose the first.
4. Name the project, then enter the base URL, which is the URL of the application you are testing. A new browser window opens on that URL and starts capturing.
5. Click through your flow, such as opening a login page, typing details and pressing Sign in. Each action appears as a command.
6. Switch back to the IDE window and click the recording icon to stop, then select your test and click the play button in the menu bar to replay it.

Each row in the editor holds a command, a target and a value. The target is a locator such as an id or CSS selector, and the value is what to type. You can edit any row after recording.

Click the save icon at the top right of the IDE to save the project as a single .side file you can reopen or hand to a colleague.

What can Selenium IDE do, and where does it stop?

It handles simple, linear flows well and starts to strain once tests need real logic, shared data or heavy maintenance. Knowing the limits saves you from building a large suite on a tool meant for small ones.

Selenium IDE also has a command-line runner, installed with npm install -g selenium-side-runner and started with selenium-side-runner /path/to/project.side. It needs Node.js and a browser driver such as chromedriver. That helps a small team run recorded checks in a pipeline, though you still depend on the recording staying correct. The runner documentation has the current options.

When should I move from record and playback to code?

Move to code once you are copying and pasting steps between tests, or when a test must run unattended on every commit. Those are signs the recording has outgrown the extension.

• You repeat the same login steps in ten tests and want one shared function.
• You need to run tests against several browsers or in headless mode.
• Tests must read test data from a file, API or database.
• A failing test needs proper logs, screenshots and retries.
• Several people edit the tests and need pull requests and history.
• You want to combine UI checks with API calls or database setup.

You do not have to throw the recording away. Selenium IDE can export a test to code: its code export docs list C# NUnit and xUnit, Java JUnit, JavaScript Mocha, Python pytest and Ruby RSpec. Right-click a test or suite, choose Export, pick a language and click Export. Treat the exported file as a draft to refactor, not a finished suite.

Some teams choose a different framework instead of Selenium. Playwright, for example, ships a code generator described at playwright.dev/docs/codegen. Which tool suits you depends on languages, browsers and what your team already knows.

If your goal is broader automation, such as filling forms or repeating clicks for yourself rather than testing, look at the automation category instead.

How do I set up Selenium WebDriver with Chrome?

Install the Selenium library for your language and let it locate ChromeDriver. Since Selenium 4.6, releases ship with Selenium Manager, which acts as a fallback to find and download a matching driver automatically when you do not provide one.

1. Install Python and run pip install selenium in a terminal, or choose the equivalent package for Java, JavaScript or C#.
2. Make sure Chrome is installed and up to date.
3. Create a file with the short script below.
4. Run it. Chrome opens, loads the page and closes.

from selenium import webdriver
from selenium.webdriver.common.by import By

driver = webdriver.Chrome()
driver.get("https://example.com")
print(driver.title)
link = driver.find_element(By.TAG_NAME, "a")
print(link.text)
driver.quit()

If Chrome fails to start, the usual cause is a version mismatch between the browser and the driver. Check the ChromeDriver documentation and the Selenium documentation for the current setup steps, since details change between releases.

Which Chrome extensions help testers alongside Selenium?

Katalon Recorder is the one recorder here. The rest do not record or replay tests; they help you inspect, reproduce and debug what your tests find. Pair them with the tool of your choice from the developer tools category.

For a wider list of tools that suit programmers, see the developers hub.

How do I handle cookies and logged-in sessions when testing?

Use a cookie editor to inspect and change cookies by hand, so you understand what your script has to set. Then reproduce that state in code with WebDriver's cookie methods.

Typical uses are checking whether a login sets a session cookie, testing what happens when a cookie expires, and confirming that a consent banner writes the right value. Editing cookies manually first shows you the exact name, domain and path you will need later.

How do I test different browsers, user agents and screen sizes?

For quick manual checks, switch the user agent and resize the window before you write a test. That tells you whether the page reacts, and which cases deserve automation.

1. Install a user agent switcher and choose a mobile or alternate browser string.
2. Reload the page and confirm it serves the layout you expect.
3. Use a window resizer to snap to common widths.
4. Note the breakpoints where the layout changes, then repeat them in a scripted test.

Remember that changing the user agent changes only a header. It does not emulate a phone's screen, touch input or performance. For those, use Chrome DevTools device mode or a real device.

You can also use our free webcam test, keyboard tester and mic test to rule out hardware problems before blaming your test script.

Why does my recorded Selenium test fail or behave differently?

Most failures come from timing, unstable locators or environment differences rather than from Selenium itself. Fix those three and most recordings settle down.

• Element not found: the page had not finished loading. Add a wait command for the element instead of a fixed pause.
• Wrong element clicked: the recorded locator matches several elements. Replace it with an id or a specific CSS selector.
• Works once, fails on replay: leftover state, such as a logged-in session or filled form. Clear cookies or start a fresh profile.
• Different results on the CI machine: the window size, browser version or locale differs from your laptop.
• Pop-ups and extensions interfere: an ad blocker or consent banner changes the page. Use a clean profile, and check for blockers with our ad block test.
• Timing-sensitive input: actions that depend on speed, like repeated clicks, may behave differently. The CPS test shows how fast you click by hand.

Network checks matter too. If a test depends on a VPN or proxy, confirm your traffic goes where you expect with the WebRTC leak test. For research-focused tools, our AI tools for researchers list is a different angle.