Smoke testing
Check the essentials before deeper testing begins.
A build that cannot log in or load its main page wastes everyone's testing time. A short, fast set of checks answers "is this build worth testing" before deeper work starts.
A smoke test is a short set of checks run first to decide whether a build is worth deeper testing.
Example scenarios
- Login with a valid account
- Access to the main pages after login
- One primary transaction (create, order or submit)
Proposed workflow
Each step names the capability it relies on and that capability's current stage. Steps that rely on a Planned capability describe intended use.
Turn user journeys into tests Planned
Define three to ten essential checks with clear expected outcomes.
Run checks consistently Planned
Run the smoke group on every deployment to staging, on demand or on a schedule.
Share results Planned
Share the pass or fail summary with the team before deeper testing is scheduled.
Sample output
Checks from the sample report that match this use case. Open a check to see its execution details.
Login with a valid account c-01 · 9sPassedExpected: Dashboard loads with the account name in the headerActual: Dashboard loaded; header shows "Sample User"Show execution detailsHide execution details
Sample screenshot
c-01 final stateScreenshot not included in this sample. - navigate /login
- fill email
- fill password
- click Sign in
- assert header text
Main pages reachable after login c-02 · 14sPassedExpected: Products, Orders and Settings return 200 and render their H1Actual: All three renderedShow execution detailsHide execution details
Sample screenshot
c-02 final stateScreenshot not included in this sample. - visit /products
- /orders
- /settings
- assert h1 on each
Primary transaction: add one item to cart c-03 · 7sPassedExpected: Cart count increments to 1Actual: Cart count 1Show execution detailsHide execution details
Sample screenshot
c-03 final stateScreenshot not included in this sample. - click Add to cart on first product
- assert cart badge = 1
Limitations
- Smoke checks confirm the essentials work; they do not replace the regression set
- Running from a CI pipeline depends on a CI integration, which is planned
What would you like to stop checking manually?
Tell us about your application and testing challenges. We'll follow up about early access and whether Testivra fits your needs.