Follow one ticketfrom QA to proof.
Smoketest is an AI QA teammate. When a ticket reaches QA, it works out what to test, tests it the way a tester would, and puts the result on the ticket with a recording. When it gets one wrong, you tell it once and it remembers.
It reads the ticket and works out what to test.
Nobody writes a test. It reads the ticket and what changed, then lists what it will check, in words your whole team can read.
| No. | Action | Expected result |
|---|---|---|
| 1 | ActionSign in as Workspace Admin and open Billing | Expected resultAdmin can open Billing |
| 2 | ActionAdd one seat from the Seats panel | Expected resultAdding one seat updates the Billing page |
| 3 | ActionOpen the invoice preview | Expected resultInvoice preview shows the proration |
| 4 | ActionDownload the invoice PDF and read it | Expected resultInvoice PDF shows the same amount |
It runs the test and brings back the proof.
It signs in with your test account and works through the change the way a tester would. The result lands on the ticket, one click from the recording.
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.
- ✓Admin can open Billing
- ✓Adding one seat updates the Billing page
- ✓Invoice preview shows the proration
- ✗Invoice PDF shows the same amount
Not tested: other invoice languages, because the ticket only covers English.
Next: moved to In Progress. Move the ticket back into QA to test again.
Watch the recording · View attempt
Correct it once and it remembers.
It will get some wrong, as any tester does. Tell it on the ticket, the way you would tell a teammate, and it carries that to every ticket after.
Failed. The invoice PDF still shows the old total.
That is the old file. The PDF takes a moment to build, so wait for the Ready badge.
Passed, 4 of 4 requirements. I will wait for the badge on every invoice ticket from now on.
Wait for the Ready badge before downloading.
Use Acme Pro for billing tickets.
Sign-in codes and receipts arrive there.
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.
You can see why in the recording. Leave a note on the ticket or move it back to QA with a comment. It tests again and keeps what you told it for next time.
Usually, but it is not a replay. It can take a different path through your app, the way two testers would. When it cannot tell, you get No Result.
No. It can test from the ticket alone. With a linked pull request it has a better idea of what to test.
Yes, the way a tester would, so point it at staging with test accounts. It cleans up after itself where it can and tells you when it could not.
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.
See this happen on one of your own tickets.
Book a call and we will run it with you on a real ticket, then read the result together.
Passed · 4 of 4 requirements · 2m 12s · Attempt 3
The invoice PDF now carries the proration line, and its total matches the preview.
Watch the recording · View attempt