Smoketest vs QA Wolf

Smoketest vs QA Wolf: two answers to the same problem.

QA Wolf is a managed service: their team plus AI builds and maintains your suite and verifies every failure. Smoketest is a self-serve product you run yourself: describe a test, and an agent re-runs it in a real browser after every deploy.

Self-serve. No onboarding project, no contract, no queue. Your first run in about two minutes.

smoketest.sh/dashboard
Board
Tickets currently moving through QA
Development1
Jira · APP-917
Invite member from workspace settings
App QANot tested
Testing2
Linear · WEB-284
Apply annual discount at checkout
Checkout QARunning
Linear · AUTH-126
Recover account with magic link
Authentication QANeeds attention
Passed1
Jira · BILL-442
Show updated invoice after seat change
Billing QAPassed
The problem

Same goal, very different shape.

QA Wolf and Smoketest both want your critical tests covered. They differ on who does the work, what you operate, and what you end up owning.

Who does the work

QA Wolf's QA engineers and AI build and maintain the suite for you. With Smoketest, you describe a test and the agent runs it.

How failures are handled

QA Wolf has a human verify every failure before it reaches you, a real strength at scale. Smoketest hands you the recording, transcript, and result to judge.

What you operate

QA Wolf runs the suite on their own cloud after an onboarding ramp. Smoketest runs in minutes, self-serve, with nothing to set up.

What you own after

QA Wolf hands back Playwright code, though it was built to run on their infrastructure. Smoketest leaves nothing to maintain.

What a test looks like

No selectors. No test file.

you write
Start on the pricing page.
Choose the Pro plan.
Create a new account with the test email.
Complete checkout with the test card.
Confirm Pro features are enabled.
smoketest does the rest
Opens a real browser and runs each step
Pulls test credentials from your Persona secrets
Records the full session
Returns a pass or fail result with its reasoning
Saves the transcript, screenshots, and a Playwright trace
Smoketest vs QA Wolf

Smoketest vs QA Wolf, at a glance.

QA Wolf
Smoketest
Model
Managed service: their team runs it
Self-serve product: you run it
Who writes tests
Their QA engineers, with AI
You describe the test; the agent runs it
When a test fails
A human verifies it before you see it
You get the recording, transcript, and result
Coverage
A broad suite, ramped over months
A few critical tests, running in minutes
Commitment
Quote and onboarding ramp for managed coverage
Start today and cancel whenever you like
Pricing
Managed coverage by custom quote; self-serve platform at published usage rates
$39/month flat, listed publicly
Who it's for

Which one fits your team?

Smoketest is the better fit when you

Are a small team shipping weekly with no QA function
Want a few critical tests watched, not a broad managed suite
Want to start today and drive it yourself, with no onboarding or contract
Want a recording, transcript, and result you control

QA Wolf is the better fit when you

Want QA taken off your plate entirely, run by their team
Need broad, deep end-to-end coverage across many tests and environments
Value a human verifying every failure before it reaches you
Are a funded team with the scale and budget for a managed service
Use cases

Cover the tests that matter.

Login

→User logs in with email and password and lands on the dashboard.

Checkout

→User adds an item, checks out with the test card, and sees the order confirmation.

Onboarding

→New user signs up, completes the setup wizard, and reaches an empty project.

Billing

→User upgrades to Pro and the workspace shows Pro features enabled.

Magic link

→User requests a magic link, opens it, and lands authenticated.

PR previews

→Your critical tests, pointed at the pull request's preview URL.
When it fails

The whole story, not just a red X.

Every failed run hands you a recording, a transcript, the result, and the downloadable Playwright trace.

signup-test.webm
00:00↑ 00:06 · sign-up00:07
step log
Opened /pricing
Clicked “Start free”
Filled email · password
Submitted sign-up form
Expected dashboard · got 500 error
Session recording
Screenshot at failure
Step-by-step transcript
Downloadable Playwright trace
How it works

Jira or Linear starts the Test.

Keep the workflow where QA already works. Smoketest adds execution, evidence, and routing without becoming another board.

workspace · connections
Lhealthy
Linear
Acme workspace
Jhealthy
Jira
acme.atlassian.net
01

Connect Jira or Linear

A workspace owner authorizes Jira or Linear once. Smoketest keeps Connection identity, permissions, token health, and webhook health visible.

new test source
Listen to
Checkout board · QA
Passed
Ready to release
Failed
Development
Run at
staging.acme.com · Desktop
Permissions and direct transitions validated
02

Define the QA handoff

Choose the team or board, exact QA status, direct Passed and Development statuses, then set the URL, Environment, device, and access settings.

test request · attempt 1
WEB-284 enters QA
Ticket + linked PR frozen
Generated Test created
Browser Run in progress
03

Let the ticket start testing

When a ticket enters QA, Smoketest freezes current context, enriches it from an eligible ticket-linked pull request, generates one Test, and runs it automatically.

result · synchronized
PASSEDWEB-2841m 42s
Attempt comment updated with evidence
Authenticated recording and transcript linked
QAReady to release
04

Return the Result safely

Smoketest posts evidence to one evolving Attempt comment. Passed moves forward, Failed returns to Development, and No Result stays in QA. Newer human changes always win.

FAQ

Teams comparing us to QA Wolf ask these.

QA Wolf prices in two ways. Their managed Coverage as a Service is quote-based, priced per test under management, and includes their team doing the work. Their self-serve platform lists usage rates of one cent per AI credit and fifteen cents per runner minute. Smoketest is $39 per month, or $32 per month billed annually, with 300 run credits, listed on the pricing page. The comparison that matters is a managed service or metered usage versus one flat self-serve price.

No. QA Wolf's team and AI build and maintain your tests and verify every failure for you. Smoketest is self-serve: you describe a test in a sentence, the agent runs it, and you read the result. Nothing to maintain, and no team in the loop.

At scale, yes. QA Wolf builds a broad suite over an onboarding ramp and aims for high end-to-end coverage. Smoketest is built to watch a handful of critical tests you can stand up in minutes. If you want comprehensive coverage handled for you, QA Wolf is the better fit.

QA Wolf hands back standard Playwright code, though it was built to run on their infrastructure, so you keep the files more than the running setup. Smoketest has nothing to own or maintain: you describe a test and the agent runs it.

QA Wolf puts a human in front of every failure, which is a genuine strength against false alarms. Smoketest's agent reads the page on each run instead of saved selectors, and hands you the recording and transcript so you can confirm a failure yourself.

If you have no QA, no time, and want a handful of money-path tests watched today, Smoketest is built for that. If you're funded and want broad coverage taken off your plate by a team, QA Wolf is the better fit.

Watch your critical tests today.

Describe one journey you can't ship broken, run it in a real browser, and get a recording and a result in minutes. Self-serve, no onboarding, no contract.

Read the docs