A sanity test checks one change narrowly: that a fix or a small new feature works, and that the things right next to it still do. A sanity checklist is the short list of those checks, written down so anyone can run them when the build arrives. The table above is a sanity test template with five 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#
- Read the examples above. Each row names the change it checks in the Change checked column, so one release can hold several changes.
- Select Download .xlsx for a workbook with a How to use tab, the examples and 15 blank rows, or Download .csv to import the rows into another tool.
- For each fix or change in a build, add a few rows: the change itself, the case that used to fail, and one or two things beside it.
- Run them as soon as the build arrives, and set Status 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. |
| Change checked | The fix or change this row is about, with its ticket or bug reference if you have one. |
| Check | One line saying what is checked about that change. |
| 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 sanity checklist for any fix#
Go through these six checks after any fix, and write a row in the template for each one that applies.
- The case that was reported now gives the expected result.
- The same steps on the previous build still show the bug, so you know the row can fail.
- The normal path through the same screen works with ordinary input.
- One wrong or empty input on that screen is refused with a message.
- The step right after the fixed one works.
- The change looks the same at a phone width, if the screen is used on phones.
What the examples show#
The examples cover two changes. For a fixed discount code, they check that the code applies, that an expired code is still refused, and that removing the code restores the total. For a new delivery date on product pages, they check that the date shows, and that an item out of stock shows none. One of those rows failed on mobile, and its note says what was seen.
Sanity testing vs smoke testing#
A smoke test is broad and shallow: a few checks across the whole app that say whether a build is worth testing. A sanity test is narrow and deeper: several checks on the one thing that changed. 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. Run the smoke test template first, then the sanity rows for each change. If you find yourself checking the whole checkout, the rows belong in the regression test template. Smoke vs sanity vs regression testing follows one release through all three.
Questions#
What is a sanity checklist?#
A short list of checks run after a fix or small change: the change itself, the case that used to fail, and the things beside it. The six checks on this page are one you can reuse.
What goes in a sanity check document?#
The change being checked with its ticket reference, the steps for each check, the expected result, the result of the run and a note for anything that failed. The template's seven columns hold these.
What is the difference between sanity and regression testing?#
Sanity tests check one change quickly. Regression tests re-check features that already worked, across the whole app, so a change does not break them unnoticed.
Should sanity rows be kept after the release?#
Keep the row for a reported bug. Move it into your regression list so the bug cannot come back unnoticed.
Is the template free?#
Yes. Download it without an account and use it in your own plans and tools.