Thunders alternative: Retracio
Thunders, previously named Thunder Code, is a cloud platform where AI agents write, run, and maintain a test suite in plain language (checked 2026-09-08). Tests execute in the Thunders cloud, on a self-hosted platform shipped as container images, or in a hybrid setup where only the browser engine runs on your side (checked 2026-09-08). Test cases are stored on the platform; export is declared, and the pricing page lists Playwright reversibility (checked 2026-09-08). Retracio is a desktop app. You walk through a scenario by hand, and it writes a plain Playwright spec into your repository, reusing the repository's page objects, fixtures, and locator style.
| Criterion | Retracio | ThundersCloud AI platform |
|---|---|---|
| Follows the conventions of your repository | Yes | No |
| Where tests run | Local or cloud | both: Thunders cloud; self-hosted full platform as container images, or hybrid with only the browser engine on the user's side |
| Who owns the test code | Plain test files in your repository | vendor format: plain-language test cases stored in the Thunders platform; export of tests declared, export format not documented |
| Works offline | ||
| Maintenance model | Edit the test like any other file | self-healing |
| Output frameworks | Playwright | playwright (listed on pricing as 'Playwright reversibility'; no documentation of the export format found) |
Alternatives checked on 2026-09-08 against their own websites and documentation. Empty cell: not confirmed.
Thunders fits when…
- Testers describe scenarios in plain language, and the team wants the suite written, executed, and repaired by agents on a platform instead of as code in a repository (checked 2026-09-08).
- Runs need to happen in the Thunders cloud, on a self-hosted platform inside your own infrastructure, or in a hybrid mode where the browser engine sits on your side and orchestration stays in the Thunders cloud (checked 2026-09-08).
- You already have Playwright, Selenium, or Cypress suites and want to import them into Thunders test cases through MCP (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 leave behind a spec with assertions, committed by a person on the team, with no recording stored elsewhere.
- 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
Who owns the test code with Thunders and with Retracio?
Thunders stores test cases in plain language on its platform. The site declares that tests can be exported and run elsewhere, and the pricing page lists Playwright reversibility; the export format is not documented (checked 2026-09-08). With Retracio, the output is a plain Playwright spec written into the folder you choose in your local checkout, with no product import, plugin, or runtime. Committing stays with you. Uninstall the app and every generated test keeps working in your CI.
Do the generated tests break when the UI changes?
Thunders answers this with self-healing: when the UI changes, the platform detects the difference and repairs steps at runtime (checked 2026-09-08). It 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. If the repo has its own locator convention, such as a data-testid prefix, the generated test follows it. When a step still fails on review, the app regenerates only that step and leaves the rest of the file untouched.
Can I use Playwright without coding?
With Thunders, the suite is written and maintained in plain language by agents, and the site states that no scripts are involved (checked 2026-09-08). With Retracio, the tester does not write code either: they walk through the scenario in the browser and mark what should be true on each screen. The app writes the Playwright spec, shows it as a diff, and runs it locally with one click.
How do the generated tests integrate with CI/CD?
Thunders runs are triggered from CI through a REST endpoint with a Bearer token, and the execution location is selected by geo cluster (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.
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.
What frameworks and languages are supported?
Thunders tests are written in plain language on the platform; the same test can be selected to run on Chrome, Firefox, Safari, and Edge without per-browser configuration, and the pricing page lists Playwright reversibility (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.
Do the generated tests follow our coding standards?
The Thunders site describes agents that write and maintain the suite in plain language with no scripts; it does not describe reading a target repository's structure, fixtures, or style (checked 2026-09-08). Retracio starts by building a conventions profile from the tests already in the repo: page objects and fixtures, file and test naming, assertion style, lint and formatter config. The generated spec lands in the same folder pattern, uses the same helpers, and passes the same lint config, so it goes through code review like a file written by a teammate.