Leapwork alternative: Retracio
Leapwork ships several products; two of them are relevant here. Leapwork Flow builds automation on a visual block canvas in a Windows Studio, stores flows in a Controller, and runs them on Agents in the customer environment or as a Leapwork-hosted service (checked 2026-09-08). Leapwork Play, in Tech Preview, records clicks in a cloud browser and generates Playwright code inside the Leapwork workspace (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.
| Criterion | Retracio | Leapwork |
|---|---|---|
| Follows the conventions of your repository | Yes | |
| Where tests run | Local or cloud | both |
| Who owns the test code | Plain test files in your repository | vendor format; Leapwork Flow stores visual flows in the Controller, Leapwork Play generates Playwright code inside the Leapwork workspace |
| Works offline | Yes | |
| Maintenance model | Edit the test like any other file | self-healing |
| Output frameworks | Playwright | playwright (Leapwork Play); Leapwork Flow uses a visual block canvas without a code framework |
Alternatives checked on 2026-09-08 against their own websites and documentation. Empty cell: not confirmed.
Leapwork fits when…
- Your team designs automation on a visual canvas without a code framework and needs on-premise, customer-hosted cloud, Leapwork Cloud, or hybrid deployment, including offline installation of Studio (checked 2026-09-08).
- Coverage spans web, desktop, green screen, and virtual applications, executed by Self-Managed Agents in your environment or by Leapwork-Managed Agents (checked 2026-09-08).
- You want Playwright generated by clicking through the app in a zero-install cloud browser, with self-healing AI repairing a broken step during the run, and Tech Preview status is acceptable (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 in the local checkout, 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
Who owns the test code with Leapwork and with Retracio?
Leapwork Flow stores visual flows as automation assets in the Controller rather than as code. Leapwork Play generates Playwright code and keeps it inside the Leapwork workspace, and existing Playwright scripts can be brought into that shared workspace (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. Uninstall the app and every generated test keeps running in your CI.
Do the generated tests break when the UI changes?
Leapwork answers this with self-healing in both products: Flow adapts workflows as applications evolve, and in Play a self-healing AI fixes the broken step instead of failing the run (checked 2026-09-08). Retracio resolves each element the tester touched to a role, label, or test-id locator and follows the repo's own locator convention, such as a data-testid prefix. When a step fails on review, it regenerates only that step and leaves the rest of the file untouched.
Can I use Playwright without coding?
Leapwork Flow uses a visual block canvas without a code framework: teams connect structured blocks on a visual canvas. Leapwork Play produces Playwright by turning each click in its cloud browser into a step and the code beneath it (checked 2026-09-08). In Retracio, a tester runs the scenario by hand in the app's browser and marks checks on each screen; the Playwright spec is generated from that session. The file is editable on the review screen before it is saved and lands in the repository shaped like the tests already there.
How do the generated tests integrate with CI/CD?
Leapwork's Enterprise Playwright offering describes generated code that runs without AI at runtime and integrates with Azure DevOps, GitHub Actions, and Jenkins (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?
Leapwork Play accepts source code as context through its Knowledge Base, imported as a zip file or cloned from a Git repository into the Leapwork workspace (checked 2026-09-08). With Retracio, the browser, the recording, the repository scan, and the test execution happen inside the desktop app. What goes out is the recorded steps, trimmed DOM snapshots of the pages under test, and excerpts of the conventions profile, 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?
Leapwork Flow builds automation on a visual block canvas without a code framework; Leapwork Play generates Playwright (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 in your repository, so it works with whatever Playwright version, reporter, and configuration your project already uses.
Do the generated tests require maintenance?
In Leapwork, maintenance is handled inside the platform: self-healing adapts Flow workflows through updates and configuration changes, and Play repairs a broken step during the run (checked 2026-09-08). With Retracio, a generated spec is maintained like any other file in the repo. It imports existing page objects instead of duplicating selectors inline, so a selector fix in the page object applies to it as well. When a scenario changes, the tester reruns it in the app and only the affected step is regenerated.