Skip to content
testcritic

Robot Framework vs Cypress

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

Free and open source

Open source

From $75 per month (Cloud Team, month-to-month; $799/year works out at $67)

Free tier

What drives the bill

The metric that actually scales your invoice.

Free and open source. You pay in engineering time and CI minutes.

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 tier

Everything, self-hosted

The test runner is free forever. Cypress Cloud free tier covers a limited number of recorded test results per month.

Open source

Apache-2.0

MIT (runner)

Self-hostable

No-code authoring

Languages

PythonJavaCodeless
JavaScriptTypeScript

Platforms

WebAPIiOSAndroidDesktop
WebAPI

Fits teams

Scale-up / mid-marketEnterprise
Solo / side projectStartupScale-up / mid-marketEnterprise

Adoption

Widely used

Robot Framework Foundation · since 2008

Category standard

Cypress.io · since 2017

Strengths

  • 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.
  • 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.

Limitations

  • 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.
  • 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.

Best for

QA-led and regulated organisations where readability by non-programmers is a requirement.

Front-end teams who value developer experience and live in a single-origin JavaScript app.

All of these integrate with: Jenkins.

Pricing last reviewed August 2026 and is indicative only — confirm on each vendor’s own page.