Describe your tests in a sentence. Smoketest re-runs them in a real browser after every deploy and tells you the moment one breaks.
No Playwright code. No selectors. Your first run in about two minutes.
Role-based locators survive some changes, but renames and restructures still break them, and keeping them current is your job.
Auto-waiting helps, but timing and environment differences still fail runs for the wrong reasons.
Writing and maintaining the suite is a job no one on a small team has time for.
Green CI doesn't mean checkout works in production right now.
Start on the pricing page. Choose the Pro plan. Create a new account with the test email. Complete checkout using the test card. Confirm the workspace has Pro features enabled.
Every failed run hands you a recording, a transcript, the result, and the downloadable Playwright trace.
Keep the workflow where QA already works. Smoketest adds execution, evidence, and routing without becoming another board.
A workspace owner authorizes Jira or Linear once. Smoketest keeps Connection identity, permissions, token health, and webhook health visible.
Choose the team or board, exact QA status, direct Passed and Development statuses, then set the URL, Environment, device, and access settings.
When a ticket enters QA, Smoketest freezes current context, enriches it from an eligible ticket-linked pull request, generates one Test, and runs it automatically.
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.
Smoketest runs your tests in a real browser through a managed agent and saves a downloadable Playwright trace with every run. You never write or maintain any Playwright code yourself.
No. You describe each test in a sentence or two and add test logins as environment variables. There are no selectors or scripts to keep alive.
Playwright's role-based locators survive some changes, but a human still writes and maintains them. Smoketest's agent re-reads the page on each run, so a renamed button or moved element does not break the test. A run fails only when the behavior actually broke.
Yes. Every failed run hands you a recording, a step-by-step transcript, a pass or fail result with the agent's reasoning, and a downloadable Playwright trace.
About two minutes for the first one: paste a URL, write the steps, run it once to confirm, then schedule it or fire it on every deploy.
Write your first test, run it in a real browser, and know in minutes whether your core journeys still work.
Read the docs