A teammate youonboard and supervise.
Smoketest is an AI QA teammate for your team. It takes the first pass on each ticket in your QA column. You set its rules, review its results, and keep the calls that need a person.
Your process stays yours.
Your columns, your rules, and your standards stay as they are. These four moments get easier.
It takes the first pass. You keep the judgment.
What moves to it
- The first pass on every ticket
- Testing again when a ticket comes back
- Logins, email codes, and test data
- Saved regression checks on each deploy
What stays with you
- The playbook it plans from
- Exploratory testing
- What counts as a release blocker
- The go or no-go call
Onboard it the way you would anyone new.
It starts from your playbook, and it takes on more of the column as you review its work.
- 1
Give it the playbook
Write down how your team tests. It plans from those rules on every ticket.
- 2
Give it test accounts
One for each role, with the sign-ins and inboxes your tickets need.
- 3
Review its first tickets
Read the plan, watch the recording, and correct it the way you would anyone new.
- 4
Hand it the column
It picks up what reaches QA. Anything it cannot settle comes back to you.
Passed · 4 of 4 requirements · 3m 04s · Attempt 1
- ✓Admin can create an invite link
- ✓A new user joins from the link
- ✓An expired link shows the right error
- ✓A Member cannot create a link
Not tested: SSO workspaces, because the ticket does not cover them.
Watch the recording · View attempt
Good. Adding SSO workspaces to the playbook for invites.
You can check everything it does.
It shows its work
Every result has the recording, the steps, and the reasoning.
It says what it left out
Each result lists what it did not test, and why.
It asks when it is not sure
A ticket it cannot settle comes back as No Result, with a question for you.
It remembers what you teach it
It learns your product as it tests, and later tickets start from what it learned.
It brings the evidence.You make the call.
Questions QA leads ask first
Reporting to engineering leadership? See what they get
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.
You do, or whoever on your team holds it today. Smoketest gives them the evidence: what passed, what failed, the recording, and what it did not test. It never signs off a release.
You can see it, because every step is on the recording. Correct it on the ticket or in the playbook, and it carries that into later tickets.
Yes. It reads the ticket, comments, and pull request, and looks at what the change touched nearby. Open-ended exploring stays with your team, and it tells you what it left out.
Yes. Put them in the playbook, and it plans from them. Your team edits the rules in one place, and every result shows which ones it applied.
No. It leaves one comment on each ticket and updates that comment as the test moves. It only changes a ticket's status the way you set it up.
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.
Bring your hardest ticket to the call.
We will run it with you and read the result together, so you can judge its work for yourself.