The fastest QA check we sell
Check the one flow that has to work before you ship
The smoke test answers one question before a release: does the thing that matters most still work? We test a single critical flow, such as sign-up, checkout, a workout log or a therapy check-in, usually within a couple of days. You get a clear pass or fail, and any defects written up with steps to reproduce.
What you get
What’s included
One critical flow, agreed up front
The full path from the first screen to the confirmation the user sees at the end, defined with you before testing starts.
Tested on the devices that matter
Run on a small set of devices or browsers agreed with you, picked from what your users own.
A plain pass or fail
A direct answer on whether the flow works, and on which devices it doesn't.
Defects a developer can pick up
Anything that fails comes with severity, environment, steps to reproduce and how often it happens.
A good fit if
- Teams pushing an update this week who want an outside check on one flow
- Supplement stores checking checkout after a theme or app change
- Studios and coaches checking sign-up or booking after a platform change
- Teams that want to try our QA on something small before booking a full cycle
Not included
- More than one flow. An exploratory cycle covers a whole feature
- Regression across the rest of the product
- A go/no-go recommendation for the whole release
- Fixing what we find
How it runs
From kickoff to handover
- Step 1
Name the flow
Tell us the flow, where to find the build or site, and your release date.
- Step 2
Test it
We run the flow end to end on the agreed devices, including the common ways users get it wrong, like going back mid-flow or entering bad details.
- Step 3
Report
Pass or fail, plus written defects, usually within a couple of days.
Questions
Questions about QA smoke test
What counts as one flow?
One start-to-finish path a user takes to get one thing done: creating an account, buying a product, booking a class, logging a workout. If it branches into several separate paths, we'll tell you before we start whether it counts as two smoke tests or needs an exploratory cycle.
How quickly do I get results?
Usually within a couple of days. Give us your release date when you book, and we'll confirm up front whether we can make it.
Is a smoke test enough before a big release?
For a small update that touches one flow, it often is. For a launch, or a release that changes several areas, it's too narrow. QA & Release Readiness or a regression cycle covers that properly.
What do you need from us?
Access to the build (a TestFlight invite, a test APK, a staging link or the live site), a test account if the flow needs one, and a sentence on what working looks like for this flow.
We ship every couple of weeks. Should we just book a smoke test each time?
You can. If you're booking one every release, ongoing QA is usually the better fit, because it adds regression, triage and release notes on top.
More from QA & Release
Keep exploring
Often paired with this
Work with us
Ready to start QA smoke test?
Tell us about your business. We'll confirm the scope and send you a start date.