Leapwork vs Testim
Feature checklists rarely decide anything. What decides it is the pricing metric, who has to write the tests, and which limitation you can live with.
Entry price
Quote on request
Quote onlyQuote on request
Quote onlyWhat drives the bill
The metric that actually scales your invoice.
Enterprise quote-based licensing, typically annual and sized by concurrent runners plus authoring seats.
Quote-based beyond the free tier; priced by annual test runs.
Free tier
Free trial.
Free plan with a limited monthly run allowance.
Open source
Self-hostable
No-code authoring
Languages
Platforms
Fits teams
Adoption
Emerging
Leapwork · since 2015
Established
Tricentis · since 2014
Strengths
- Genuinely usable by non-technical staff — the flowchart model is easier than any script-behind-a-recorder approach.
- Covers Citrix, virtual desktop and mainframe environments that most tools cannot touch.
- Doubles as an RPA platform, which can consolidate two budgets.
- Smart locators handle everyday UI churn well.
- The escape hatch to real JavaScript keeps complex cases possible.
- Reusable shared steps keep large recorded suites maintainable.
Limitations
- Flowcharts do not diff or merge, so version control is essentially unusable.
- Complex logic becomes an unreadable sprawl of blocks.
- Enterprise pricing with no small-team entry point.
- Test logic lives in the vendor's cloud rather than your repository, which complicates review and branching.
- Run-based pricing punishes running the full suite on every commit.
- Post-acquisition roadmap is bound to the wider Tricentis strategy.
Best for
Enterprises where business users must own automation and Citrix or mainframe is in scope.
Teams with fast-changing UIs that need maintenance to stay low.
All of these integrate with: Jira, Jenkins.
Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.