TestFinch

Smoke test template

A smoke test template with worked examples: the few checks that say a new build is worth testing.

Smoke tests are a short list of checks that the most important paths work at all, run on every new build before anything else. If one fails, the build is not worth testing further. Examples are for an example online shop; replace them with your own app's.

Download .xlsxDownload .csvDownload .md

6 examples and 20 blank rows, with a How to use tab in the .xlsx

Smoke: 6 worked examples
IDAreaCheckStepsExpected resultStatusNotes
SMK-01HomeThe home page loads
  1. Open the home page
The page loads with no error, and the main menu and search box show.Passed
SMK-02Sign inA registered user can sign in
  1. Open Sign in
  2. Enter a test account's email and password
  3. Select Sign in
The account page opens with the user's name.Passed
SMK-03SearchSearch returns results
  1. Type 'shoes' in the search box
  2. Press Enter
A list of matching products shows.Passed
SMK-04CartA product can be added to the cart
  1. Open any product
  2. Select Add to cart
The cart count goes up by one.FailedCart count stayed at 0
SMK-05CheckoutThe checkout page opens
  1. Add a product to the cart
  2. Open the cart
  3. Select Checkout
The checkout form shows the product and the total.BlockedBlocked by SMK-04
SMK-06Sign outA user can sign out
  1. While signed in, open the account menu
  2. Select Sign out
The home page shows Sign in again.Not run

FlowQA's agent explores your site and writes cases like this one as tests, keeping each only once it has passed twice and failed on a deliberately broken page. Free to start.

Try FlowQA free

The manual case

SMK-02 A registered user can sign in

  1. Open Sign in
  2. Enter a test account's email and password
  3. Select Sign in

Expected: the account page opens with the user's name.

The FlowQA test

account/sign-in

  1. navigate "/sign-in"
  2. fill "Email" with "mia@acme.example"
  3. fill "Password" with "••••••••"
  4. tap button "Sign in"
  5. assert url matches "/account"
  6. assert text "Mia Chen" is visible

An illustration with sample data.

A smoke test is a short list of checks that the most important paths of an app work at all, run on every new build before any other testing. The table above is a smoke test template with six worked examples for an example online shop, and you can download it as an Excel workbook, a CSV file or Markdown.

How to use it#

  1. Read the examples above: each row names an area, one check, numbered steps and an expected result you can see.
  2. Select Download .xlsx for a workbook with a How to use tab, the examples and 20 blank rows, or Download .csv to import the rows into another tool.
  3. Replace the examples with your own app's most important paths, and keep the list short.
  4. Run it on every new build before any other testing, and set Status to Passed, Failed or Blocked as you go.

What each column means#

Column What goes in it
ID A short, unique reference, so a result or a bug can point at this row.
Area The part of the app the check covers, such as Sign in, Search or Checkout.
Check One line saying what is checked, such as 'A signed-in user can open the cart'.
Steps What to do, one numbered action per line, written so someone new to the app can follow them.
Expected result What should happen if the app works. Write something you can see or check, not 'works correctly'.
Status The result of the last run: Not run, Passed, Failed or Blocked.
Notes Anything that helps the next person: a bug link, test data used, or why a row is blocked.

A smoke test checklist for a web app#

Write a row for each of these that applies to your app.

  • The home page loads with no error.
  • A new person can sign up, if sign-up is open.
  • A registered person can sign in and sign out.
  • The main page after sign-in shows its data.
  • The one thing people come to do can be started and finished.
  • Search or the main list returns results.
  • Payment opens, if you charge.
  • A page that needs sign-in sends a signed-out visitor to sign in.

What a smoke test is for#

A smoke test tells you whether a build is worth testing further. If the home page does not load or nobody can sign in, there is no point running two hundred detailed checks against it. The list has one check for each part of the app that the rest depends on. In the examples, a failed check on the cart blocks the checkout check after it, and the Notes column says so. When a smoke check fails, stop, report it, and wait for a new build.

Keeping it small#

Ten to twenty rows is usually enough, and the whole list should take minutes. Pick the paths that would stop most of your users: opening the app, signing in, the main thing people come to do, and paying if you charge. Leave edge cases, wrong input and rare settings to your regression and functional tests.

Smoke testing vs sanity testing#

A smoke test checks the whole build broadly before deeper testing. A sanity test checks one fix or change narrowly, with the things right next to it, and has its own sanity test template. Smoke rows stay the same from build to build, and sanity rows are written for each change. Some teams use the two names for the same quick check of a build, and the ISTQB glossary, read on 18 November 2026, defines smoke testing and has no entry for sanity testing. Smoke vs sanity vs regression testing follows one release through all three.

Questions#

What is a smoke test checklist?#

The list of checks a smoke test runs: one for each path the rest of the app depends on, such as loading, signing in and the main action. The eight items on this page are a starting list for a web app.

How often should a smoke test run?#

On every new build that will be tested or released, and again on production after each deploy.

Should a smoke test be automated?#

Yes, once the rows stop changing. The steps are the same on every build, so a script can run them after each deploy.

Is the template free?#

Yes. Download it without an account and use it in your own plans and tools.

Will these examples fit my app?#

No. They are for an example online shop and show what a well-written row looks like. Replace them with your own app's paths.