Welcome to Smoketest
Move a Jira or Linear ticket into QA and get an automated browser Test, evidence, and a routed Result.
Smoketest turns the QA handoff in Jira or Linear into tested work. Move a ticket into the configured QA status; Smoketest builds a generated Test from the latest ticket context and linked pull request, runs it in a real browser, posts evidence, and safely moves the ticket forward or back to development.
The primary workflow
- Connect a Jira Cloud site or Linear workspace.
- Create a Test Source for a team or board and select the exact QA, passed, and development statuses.
- Move a ticket into QA.
- Follow its Test Request and live browser Run in the Board.
- Receive a Passed, Failed, or No Result outcome with authenticated evidence and ticket sync history.
Smoketest does not replace Jira or Linear. Jira or Linear keeps assignment, priority, ordering, and workflow ownership; Smoketest mirrors the configured workflow in a read-only Board and owns testing execution, evidence, and safe Result routing.
What QA teams get
- Automatic QA pickup from the status your team already uses
- Context-aware generated Tests from the ticket and an eligible ticket-linked pull request
- Real browser execution with live progress, video, transcript, and structured evidence
- Safe workflow updates that honor newer human status changes
- One evolving ticket comment per Attempt rather than progress spam
- Operational Analytics for queue age, QA-to-Result time, Result mix, source health, and sync latency
Reusable Tests
The Test Library remains available for editable Tests you want to schedule, run on demand, trigger from GitHub or deployments, or manage through the API, CLI, and MCP. Generated Tests stay immutable and separate unless you explicitly save a reusable copy.
Ready to set up the QA handoff? Get started →