Cypress vs Robot Framework
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
From $75 per month (Cloud Team, month-to-month; $799/year works out at $67)
Free tierFree and open source
Open sourceWhat drives the bill
The metric that actually scales your invoice.
You only pay for Cypress Cloud. Team is $75 month-to-month or $799/year; Business is $3,199/year. Costs scale with recorded test results, so a large suite on every PR is the expensive shape.
Free and open source. You pay in engineering time and CI minutes.
Free tier
The test runner is free forever. Cypress Cloud free tier covers a limited number of recorded test results per month.
Everything, self-hosted
Open source
MIT (runner)
Apache-2.0
Self-hostable
No-code authoring
Languages
Platforms
Fits teams
Adoption
Category standard
Cypress.io · since 2017
Widely used
Robot Framework Foundation · since 2008
Strengths
- The interactive runner is the best onboarding experience in E2E testing; a new developer writes a passing test in minutes.
- Excellent documentation and one of the largest plugin ecosystems.
- Component testing and E2E in one tool with one config.
- Non-developers can read and often write the tests, which matters in QA-led organisations.
- Extends far beyond browsers: databases, SSH, serial, network equipment.
- Extremely stable and well-supported in regulated and telecom environments.
Limitations
- Runs in the same event loop as your app, which historically meant no multi-tab, multi-origin or iframe-heavy testing without workarounds. Support has improved but the model still constrains you.
- JavaScript and TypeScript only.
- Meaningful parallelisation effectively requires paying for Cypress Cloud.
- The keyword abstraction fights you once logic gets complex; you end up writing Python behind the keywords anyway.
- Verbose syntax and whitespace-sensitive files that are awkward to review in a diff.
- Feels dated next to modern JavaScript tooling, and hiring is harder.
Best for
Front-end teams who value developer experience and live in a single-origin JavaScript app.
QA-led and regulated organisations where readability by non-programmers is a requirement.
All of these integrate with: Jenkins.
Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.