Smoketest
Log inBook a call
AI QA team member

Your next QA hirestarts today.

Smoketest joins your team like a new QA engineer. It learns how you ship, takes every ticket that reaches QA, and tests it on web, mobile, API, MCP, and AI agents. You get the result and the proof on the ticket.

Book a callTalk to our founder. Test a real ticket the same day.
Acme › Active issuesPick a ticket and send it to QACycle 31
In Progress3
Ready for QA1
Done1
ACM-412K
Show proration when a seat is added
Passed, 4 surfacesFailed, sent backNo Result
ACM-418ML
Retry failed webhooks with backoff
Passed, 2 surfacesFailed, sent backNo Result
ACM-421K
Add the search_invoices tool
Passed, 2 surfacesFailed, sent backNo Result
ACM-427ML
Pay with Apple Pay at checkout
Passed, 2 surfacesFailed, sent backNo Result
ACM-406ML
Show updated invoice after seat change
Passed, 2 surfacesFailed, sent backNo Result

You get one result with the proof for each surface.

JiraLinearGitHubSlackDiscordVercelClaude CodeCursor

Your developers got faster. Your QA team did not.

AI tools put more finished work in front of QA every sprint. The same few people have to check all of it, or developers check their own work and hope. A new hire takes months to find. The tickets are in the column now.

It onboards like anyone else on the team.

No test code to write, and no new tool for your team to live in. It learns your product as it tests and uses that memory on later tickets.

Day 1, morning

Gets its access

Connect Jira or Linear and GitHub. Save staging logins and test accounts.

LinearConnected
GitHubConnected
Staging loginSaved
Test accounts3
Day 1, afternoon

Learns your process

It reads your QA statuses, your tickets, and the playbook your team writes.

WatchesReady for QA
Passed goes toDone
Failed goes toThe author
Playbook14 rules
Day 2

Takes its first tickets

Every ticket in QA gets a plan, a test, and a result. Your team checks its work.

ACM-412Failed
ACM-418Passed
ACM-421Passed
ACM-427No Result
Week 2 on

Tests every ticket

Passed tickets become regression tests that run on every deploy.

Ticket testsEvery ticket
RegressionEvery deploy
ProductionYour call
Sign-offYour team

Tell it how things work around here.

Write down how your team does QA, the way you would for a new hire. Smoketest reads it before every ticket, and each result shows which rules it applied.

See how onboarding works→
How we QA at Acme3 of 14 rules applied
01
Billing tickets run on EU staging as a workspace Admin.Applied on ACM-412
02
Anything that touches checkout also runs on iOS and Android.
03
Amounts must match across web, iOS, the API, and MCP.Applied on ACM-412
04
P0 tickets wait for Sara's sign-off before Done.
05
Failed tickets go back to the author, not the reviewer.Applied on ACM-412

Give it any ticket. It works out the test.

One team member for everything you build. A single ticket can run on all of it at once.

In QA nowACM-412Show proration when a seat is addedCloud browseriOS simulatorAPI runnerMCP clientAgent chat

It also reads emails, downloaded files, and PDFs when a ticket depends on them.

Building something else? One team asked us to test their voice agent, so we are adding it. Propose your surface

Review its work like anyone else's.

It did not write the code, so it has no reason to go easy on it. Open any result to watch the recording, read the steps, and see what it left out. At the end of the sprint you get the totals.

Example sprint
47Tickets tested
72%Passed on the first try
10Sent back to the author
3Asked a human

Hiring takes months. Smoketest takes a call.

QA engineerManaged QA serviceSmoketest
StartsQA engineerAfter the hiring loop and a notice periodManaged QA serviceAfter scoping and a suite buildSmoketestToday
CostQA engineer$104,300 median salary, before benefitsManaged QA servicePriced by quoteSmoketestFrom $399 a month, shaped to your team
Your processQA engineerLearns it over weeksManaged QA serviceYou fit their workflowSmoketestReads your playbook and tickets
CoverageQA engineerWhat they have time forManaged QA serviceMostly regression suitesSmoketestEvery ticket, on every surface
Judgment callsQA engineerThe best optionManaged QA serviceDepends on the teamSmoketestAsks your team

Salary is the U.S. median for software QA analysts and testers (BLS, May 2025).

Questions before you book a call

No. It takes the first pass on every ticket, so your QA engineers can spend their time on exploratory testing, edge cases, and sign-off. Teams use that room to ship more, not to cut people.

It reads your statuses, your tickets, and the playbook your team writes. The rules live in one place, every result shows which ones it applied, and it remembers what it learns about your product as it tests.

It reads the ticket, comments, files, and linked pull request, then works out which surfaces the change touches and which sandbox each check needs.

It says so. The ticket stays in QA with a note on exactly what was missing. A human status change always wins.

Claude Code is good for a quick check while you build. The catch is that the agent that wrote the change is then grading its own work. Smoketest starts from the ticket, did not write the code, and leaves the proof where your team reviews it.

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.

Web apps, iOS and Android apps, APIs, MCP servers, and AI agents. A single ticket can run on all of them at once. If you are building something else, email hi@smoketest.sh and we will look at a sandbox for it.

Give it one ticket.

Book a call and we will run it on a real ticket with you, then shape Smoketest around how your team ships.

Book a call
Role
QA team member
Reports to
Your QA lead
Works in
Jira, Linear, GitHub, Slack
Tests
Web, mobile, API, MCP, AI agents
Start date
Today