Updated November 2026

Cypress or Smoketest?

Choose Cypress when your front-end engineers want to write tests next to their code. Choose Smoketest when you want each ticket tested as it reaches QA, with no test code to write, from $399 a month.

Book a callTalk to our founder. If Cypress is the better fit, we will say so.
A Cypress test asks for thisseat-picker.tsx
-<button className="add">+<button data-cy="add-seat">
Smoketest asks for no change to your code

Cypress is a great way to write tests.Smoketest is for when nobody has time to.

Here is one ticket,handled both ways.

Front-end teams love Cypress for good reason: it is a pleasure to write and debug tests in. The difference is who does the work.

Acme Billing / ACM-436

Show proration on the invoice PDF

When an Admin adds a seat mid-cycle, the invoice PDF should carry the proration line and match the invoice preview.

With CypressWaits until someone writes a test for it
GA
GitHub ActionsAPPCI run

1 failing. invoice-pdf.cy.ts

Timed out retrying: expected $294.00 to equal $312.40.

What you get: an exact failure from a test your team wrote and looks after.
With SmoketestPicks it up as soon as it reaches QA
SmoketestAPP

Failed · 1 of 4 requirements not met · 2m 38s · Attempt 1

The invoice PDF leaves out the proration line. The preview says $312.40 and the PDF says $294.00.

Next: moved to In Progress. Move the ticket back into QA to test again.

Watch the recording · View attempt

What you get: a test written from this ticket, with the proof left on the ticket.

The same eight questions, asked of both.

Cypress
Smoketest
Where work starts
When someone writes a test
When the ticket reaches QA
Who decides what to test
Your engineers
It does, from the ticket, pull request, and playbook
Where proof lands
Your CI run, or Cypress Cloud
Result, recording, and steps on the ticket
Surfaces
Web apps and their components
Web, mobile, APIs, MCP servers, and AI agents
Who keeps checks current
Your engineers
Smoketest, by following the goal as screens change
Time to first result
Once someone has written the test
The day you start
Cost model
Free and open source, with Cloud from $67 a month
From $399 a month, shaped to your team
Who owns the release decision
A named person on your team
A named person on your team

Some teams should stay with Cypress.

Here is how we would decide if we were in your seat. On a call we will tell you which side you are on.

Choose Cypress when

  • Your front-end engineers want tests next to their code
  • You want component tests as well as end-to-end tests
  • You have people with time to look after the suite

Choose Smoketest when

  • Nobody has time to write or look after tests
  • You want every ticket tested the moment it reaches QA
  • You want to start this week, from $399 a month

You can run both.

Keep your Cypress tests for the components and flows your engineers own. Smoketest takes the new work on each ticket, where nobody has written a test yet.

Our founder sets it up with you on a real ticket.

  1. A call with our founder

    Tell us how your team ships and where tickets wait. We will tell you whether it fits.

  2. A real ticket, same day

    We set it up with you on your own board, so it can start the day of the call.

  3. A plan shaped to you

    It starts from $399 a month. Scale is designed with teams that need more runs.

  4. It changes as you do

    New flows, new tools, a new QA hire. We keep adjusting it with you as you grow.

Questions about Cypress

Laying out every option? See them side by side

The Cypress App is free and open source. Cypress Cloud has a free plan, then Team from $67 a month and Business from $267 a month, both billed annually, and Enterprise on a quote.

It starts at $399 a month for 1,000 runs. Each run is up to 10 minutes, and a longer test counts as two runs or more, one for every 10 minutes. If your team needs more, we design a Scale plan with you, so you stop buying extra runs.

No. Keep them. Smoketest starts from your tickets, so it does not need your tests, and the two run side by side.

No. There is nothing to add to your code, and nothing to install in your repo.

Yes. It goes where a person would go, through a payment page, a sign-in on another domain, or an email in its own inbox.

Besides web apps, it tests mobile apps on iOS simulators and Android emulators, APIs from your OpenAPI spec, MCP servers, and AI agents.

Every result links to the recording, the steps, and the reasoning, and says what it did not test, so you can check its work the way you would check a teammate's.

A named person on your team. Smoketest gives them the evidence: what passed, what failed, the recording, and what it did not test. It never signs off a release.

Give it the ticket nobody got to.

Book a call and we will test it with you. You get the result and the recording the same day.

Ready for QA
Done
ACM-436
Show proration on the invoice PDF
Passed, recording