Move a ticket to QA. Get a tested Result back.
Smoketest picks up Jira and Linear tickets in QA, creates and runs a browser Test from the latest context, posts evidence, and safely routes the ticket.
Connect Jira or Linear · 14-day free trial · No card required
QA work starts before the browser opens.
Manual testing is not just clicking through the product. The expensive part is rebuilding context and coordinating the result every time a ticket reaches QA.
That handoff lives in Jira or Linear already, but testing tools usually ask QA to recreate it somewhere else: another test case, another queue, another status to keep current.
Smoketest starts from the status your team already uses. It picks up the ticket, prepares the Test, runs the browser, returns evidence, and routes the same ticket safely.
- 01
Ticket reaches QA. A tester opens it, finds the right build, reads the thread, and asks which pull request actually changed the behavior.
- 02
Context gets rebuilt. Acceptance criteria, comments, credentials, device, and code changes are gathered by hand before testing can even start.
- 03
The same path runs again. QA repeats familiar browser steps, captures evidence, writes a summary, and decides where the ticket should go next.
- 04
The board needs babysitting. Someone posts the Result and moves the ticket, unless a newer human change makes that transition unsafe.
Your issue tracker starts the Test.
Keep the workflow where QA already works. Smoketest adds execution, evidence, and routing without becoming another board.
Connect Jira or Linear
A workspace owner authorizes the tracker once. Smoketest keeps Connection identity, permissions, token health, and webhook health visible.
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.
Let the ticket start testing
When a ticket enters QA, Smoketest freezes current context, enriches it from an eligible tracker-linked pull request, generates one Test, and runs it automatically.
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.
Give QA the Result, not the busywork.
Smoketest handles repeatable preparation, execution, evidence, and ticket routing while your team keeps ownership of judgment and the workflow in Jira or Linear.
Less manual repetition
Every QA arrival becomes an Attempt automatically, so testers spend their time on judgment and exploration instead of replaying routine paths.
Context ready at pickup
The latest ticket and an eligible tracker-linked pull request are frozen into the Attempt before its Test is generated.
Evidence with the Result
Passed, Failed, or No Result comes with authenticated video, transcript, and requirement-level evidence.
Safe routing back
Passed moves forward, Failed returns to development, and No Result stays in QA. A newer human status change always wins.
Built for the QA handoff.
The pieces that turn an issue status into trustworthy testing work, without creating another tracker for your team to maintain.
Exact QA pickup
Listen to one Linear status or a Jira board column mapped to the exact workflow status that starts testing.
Linked-PR context
Add bounded code context only when the tracker links a pull request from a repository connected to the same project.
One Test per Attempt
Generate one immutable Test from the latest bounded context, then keep every QA cycle in the same durable Test Request history.
Passed, Failed, No Result
Evidence decides the product Result. Tracker synchronization stays separate, visible, and retryable when an external update fails.
One evolving comment
Update a single Attempt comment from started to final instead of filling the ticket with progress messages.
Operational Analytics
Watch queue age, QA-to-Result time, source health, Result mix, attention causes, and tracker-sync latency.
Environment and access
Freeze a starting URL, device, Environment, saved login session, optional inbound email, and HTTP authentication into the Attempt.
Reusable Test Library
Keep schedules, GitHub triggers, deployment webhooks, tags, and Shared Steps as a separate path for maintained regression Tests.
API, CLI, and MCP
Manage and run reusable Tests programmatically without exposing tracker routing or generated Test mutation.
Issue-aware notifications
Email, Slack, and Discord identify the Test Source and ticket without copying restricted issue content or evidence.
One plan. No sales call.
Start with a 14-day trial and 50 credits, no card. Connections, Test Sources, routing, evidence, Analytics, and the reusable Test Library are included.
More than 10 seats, or need SAML SSO? Book a demo.
- Jira Cloud and Linear Connections
- Unlimited Test Sources, projects, and Tests
- 300 credits per month
- Up to 10 seats, 4 concurrent browser Runs
- Testing Queue, evidence, routing, and Analytics
- Reusable Tests with schedules, GitHub, API, CLI, and MCP
- Slack, Discord, and email notifications
Frequently asked questions.
Tracker ownership, routing safety, code context, credits, evidence, and the reusable Test Library. Anything else, ask in support chat.
No. Jira or Linear remains authoritative for assignment, priority, and workflow state. Smoketest listens to the exact QA status, owns testing execution and evidence, then updates and safely routes the same ticket. Its Testing Queue is an operational view of work being tested, not a second Kanban board.
Smoketest creates or reopens one durable Test Request, queues a new Attempt, and re-fetches the latest context when execution starts. It generates one immutable Test, runs it in a real browser, posts the Result with authenticated evidence, and applies the configured direct transition when it is still safe.
Passed moves to your configured success status. Failed returns to your configured development status. No Result stays in QA with an explanation. Smoketest re-fetches the ticket before changing it, and a newer human status change always overrides automation.
Yes, only when the tracker ticket links a pull request from a GitHub repository connected to the same Smoketest project. Smoketest uses bounded changed-file context rather than ingesting the whole repository. Missing code access is recorded but never blocks testing.
The human change wins. Leaving QA cancels queued or active work, and Smoketest will not route the ticket afterward. If the ticket later returns to QA, the same Test Request receives a new Attempt and keeps the previous history.
Tracker work stays visible and queued without creating ticket comments. When credits return, Smoketest revalidates the ticket, Connection, and Test Source before resuming automatically. One classified infrastructure retry may reuse the frozen Test within the same Attempt without another charge.
Yes. Reusable Tests live in the secondary Test Library and can run on demand, on schedules, from GitHub, from deployment webhooks, or through the API, CLI, and MCP. A generated Test never activates those triggers. Saving one as reusable creates an independent editable copy.
Each Run can include a video recording, transcript, Playwright trace, logical step history, and requirement-level evidence. Tracker comments link to authenticated Smoketest evidence rather than exposing recordings publicly or copying restricted artifacts into Jira, Linear, Slack, or Discord.
Run recordings are stored securely, encrypted at rest, and scoped to your workspace; no other workspace can access them. We don't use your tests or recordings to train models. You can delete runs and recordings at any time.
Stop rebuilding ticket context by hand.
Connect the tracker, choose the QA status, and let the next ticket arrive with a tested Result and evidence attached.
Connect your QA workflowConnect Jira or Linear · 14-day free trial · No card required