Updated November 2026

Selenium or Smoketest?

Choose Selenium when your engineers want full control of their test code, in the language they already use. Choose Smoketest when you want each ticket tested as it reaches QA, with no framework to run, from $399 a month.

Book a callTalk to our founder. If Selenium is the better fit, we will say so.
What your team looks after
With SeleniumTest codeLocators and waitsBrowser driversSelenium GridCI runners
With SmoketestYour ticketNothing else to run

With Selenium, your team runs the whole setup.With Smoketest, each ticket comes back tested.

Here is one ticket,handled both ways.

Selenium has been the standard for browser automation for a long time, and it runs in almost any language and browser. 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 SeleniumWaits until someone writes a test for it
CI
Your CIAPPNightly run

1 failed. InvoicePdfTest.java

Expected $312.40 but was $294.00. The screenshot is in the build artifacts.

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.

Selenium
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 logs and reports
Result, recording, and steps on the ticket
Surfaces
Web apps, in almost any browser
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, plus your team's time and machines
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 Selenium.

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 Selenium when

  • Your tests need to live in Java, Python, C#, or Ruby
  • You need a browser most newer tools leave out
  • You have engineers to look after the suite and the Grid

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 Selenium suite for the flows it already guards. 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 Selenium

Laying out every option? See them side by side

Selenium is free and open source. The cost is your team's time to write and look after the tests, plus the machines or the Grid they run on.

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. It runs in the cloud, so there is no Grid, driver, or browser for your team to keep up to date.

It follows the goal of the test, so a renamed button or a moved field does not fail it. If the behavior really changed, it tells you.

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.

Try it on a ticket your suite does not cover.

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