Cypress is a strong framework for engineers who write and own their specs. Smoketest re-runs your tests from a sentence and tells you the moment one breaks, with no spec files to keep alive.
No spec files. No selectors. Your first run in about two minutes.
Cypress made browser tests nicer to write, but every test is still a spec your team authors, reviews, and keeps current as the app moves.
Every test is a spec file your team writes, reviews, and keeps green.
Reliable element selection usually means adding and maintaining data-cy attributes across the app.
Specs and selectors are code, owned by whoever on the team writes JS or TS.
Cypress runs the specs you've coded in CI. It isn't built to monitor your live product after each deploy.
Start on the home page. Start a free trial. Reach the paywall. Confirm the upgrade prompt appears.
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.
For end-to-end tests on a few critical journeys, yes. If you also use Cypress for component testing or its time-travel debugger, keep it for those and let Smoketest watch the user-facing tests in production.
No. You describe each test in a sentence or two. There are no spec files, selectors, or data-cy attributes to maintain.
Yes. Point a test at a pull request's preview deployment or your live app, and run it on every deploy or on a schedule.
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 test: paste a URL, write the steps, run it once to confirm, then schedule it.
Pick a journey you'd hate to ship broken, describe it in a sentence, and run it in a real browser. No spec file required.
Read the docs