Selenium IDE alternative: Retracio
Selenium IDE is open source record and playback test automation for the web, published under the Apache License 2.0 (checked 2026-09-08). It stores recordings in a .side project file, replays them locally or on a Selenium Grid through its command-line runner, and can export a test or suite to Selenium WebDriver code (checked 2026-09-08). Retracio is a desktop app. You walk through a scenario by hand, mark what should be true on each screen, and it writes a plain Playwright spec into your repository, reusing the page objects, fixtures, and locator style already there. The file has no vendor import.
| Criterion | Retracio | Selenium IDERecord and playback |
|---|---|---|
| Follows the conventions of your repository | Yes | No |
| Where tests run | Local or cloud | both |
| Who owns the test code | Plain test files in your repository | both: .side project file and exported WebDriver code |
| Works offline | ||
| Maintenance model | Edit the test like any other file | manual (fallback among locators recorded at capture time) |
| Output frameworks | Playwright | Selenium WebDriver: C# NUnit, C# xUnit, Java JUnit, JavaScript Mocha, Python pytest, Ruby RSpec |
Alternatives checked on 2026-09-08 against their own websites and documentation. Empty cell: not confirmed.
Selenium IDE fits when…
- Your suite is built on Selenium WebDriver, and the team wants recordings that export to C# NUnit, C# xUnit, Java JUnit, JavaScript Mocha, Python pytest, or Ruby RSpec (checked 2026-09-08).
- Tests are kept as .side projects and replayed through the command-line runner, on your own Grid or on a hosted provider (checked 2026-09-08).
- Locator maintenance is handled at playback time by trying the other locators recorded for the element until one succeeds (checked 2026-09-08).
Retracio fits when…
- Your E2E suite already lives in the repository as Playwright, and every new spec has to pass the same review, lint, and formatter config as the ones written by hand.
- Testers already walk through scenarios manually and want each run to end with a spec file that carries assertions, committed by a person on the team.
- Security review requires that source code, cookies, and credentials stay on the machine and that the model is called through an API key the company controls.
Questions
How does AI test generation differ from record and playback?
Selenium IDE records the actions you take and replays them, storing multiple locators per element so playback can try another one when the first fails (checked 2026-09-08). During a Retracio session the tester also marks what should be true on each screen, and every mark becomes an assertion in the output. The result is a source file in your repository, shaped like the tests already there, importing existing page objects rather than repeating selectors inline.
Who owns the test code with Selenium IDE and with Retracio?
Selenium IDE keeps tests in a .side project file and lets you export a test or suite to WebDriver code by choosing a target language, so the team holds both the project and the exported code (checked 2026-09-08). With Retracio, the output is a plain Playwright spec written into the folder you choose in your local checkout. The file has no product import, plugin, or runtime, so it keeps running in your CI after the app is uninstalled.
Do the generated tests break when the UI changes?
Selenium IDE records multiple locators for each element it interacts with, and if one fails during playback the others are tried until one is successful (checked 2026-09-08). Retracio resolves each element the tester touched to a role, label, or test-id locator and falls back to CSS or XPath only when nothing else exists. When the repo has its own locator convention, such as a data-testid prefix, the generated test follows it. If a step still fails on review, only that step is regenerated and the rest of the file stays untouched.
Do the generated tests follow our coding standards?
The Selenium IDE documentation describes locators captured while recording; it does not describe reading the target repository's structure, fixtures, or style (checked 2026-09-08). Retracio starts by scanning the repository and building a conventions profile: framework, existing page objects and fixtures, file and test naming, assertion style, lint and formatter config, custom helpers. The generated spec lands in the same folder pattern as similar tests and passes the same lint config. You can edit it on the review screen before it is saved.
What frameworks and languages are supported?
Selenium IDE exports to Selenium WebDriver code in C# NUnit, C# xUnit, Java JUnit, JavaScript Mocha, Python pytest, and Ruby RSpec (checked 2026-09-08). Retracio writes Playwright in TypeScript or JavaScript today; Cypress and WebdriverIO, along with Python and Java output, are planned. The app runs on macOS and Windows. The output is a normal spec file, so it works with the Playwright version and configuration your project already uses.
Does my source code leave my machine?
No. The browser, the recording, the repository scan, and the test execution happen inside the desktop app on your computer. What goes out is the recorded steps, trimmed DOM snapshots of the pages under test, and excerpts of the conventions profile (page objects, fixtures, naming), sent to Anthropic Claude through an API key you provide. Source code, generated tests, cookies, screenshots, and credentials stay local. The app reads the local checkout only and never clones or uploads the repository.
How do the generated tests integrate with CI/CD?
Selenium IDE ships a command-line runner that replays .side projects and can target a Grid, either your own or a hosted provider, with the capabilities you specify (checked 2026-09-08). Retracio does not run your pipeline. The spec it writes is standard Playwright, so the job that already runs your suite picks it up with no extra step. GitHub Actions and GitLab CI are supported today; Jenkins, Azure Pipelines, and CircleCI are planned.