TestFinch

Regression test template

A regression test template with worked examples, priorities and a last-run date for each row.

Regression tests re-check features that already worked, so a new change does not quietly break them. Keep them up to date, and run the High priority rows on every release. Examples are for an example online shop; replace them with your own app's.

Download .xlsxDownload .csvDownload .md

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

Regression: 6 worked examples
IDFeatureTitlePreconditionsStepsExpected resultPriorityLast runStatus
REG-01AccountChange the passwordSigned in as a test user
  1. Open Account settings
  2. Enter the current and a new password
  3. Select Save
  4. Sign out and sign in with the new password
Sign in works with the new password and fails with the old one.High2026-10-01Passed
REG-02SearchFilters narrow the resultsNone
  1. Search for 'shirt'
  2. Choose the filter Size M
Only shirts in size M show, and the result count updates.Medium2026-10-01Passed
REG-03CartThe cart survives a reloadA product in the cart
  1. Reload the page
The cart still holds the product and its quantity.High2026-10-01Passed
REG-04CheckoutCard payment completesA product in the cart, a test card
  1. Open Checkout
  2. Enter the address and the test card
  3. Select Pay
An order confirmation shows with an order number, and an email arrives.High2026-10-01Failed
REG-05OrdersPast orders are listedSigned in as a user with orders
  1. Open Account, then Orders
Every past order shows with its date, total and status.Medium2026-09-24Passed
REG-06EmailsThe password reset email arrivesA registered email address
  1. Select Forgot password
  2. Enter the email
  3. Open the email and follow the link
The link opens a form to set a new password.High2026-09-24Not 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 regression test re-checks a feature that already worked, so a new change does not break it unnoticed. A regression test template is the list of those checks, kept from release to release, with a priority and a last-run date on each row. The table above is that 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 has a feature, preconditions, numbered steps, an expected result, a priority and the date it last ran.
  2. Select Download .xlsx for a workbook with a How to use tab, the examples and 25 blank rows, or Download .csv to import the rows into another tool.
  3. Write one row for each behaviour your users rely on, and give it a priority: High for what would stop people, Medium for the rest.
  4. On each release, run the High rows at least, update Last run, and set Status.

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.
Feature The feature the row protects, so you can run all rows for one feature after it changes.
Title A short name for the check, readable in a list.
Preconditions What must be true before the first step: who is signed in, what data exists, which page is open.
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'.
Priority How much it matters if this fails: High, Medium or Low. Run High first when time is short.
Last run The date of the last run, so stale rows stand out.
Status The result of the last run: Not run, Passed, Failed or Blocked.

Reading the examples#

Preconditions let each row start without reading the one before it. Priority decides what runs when there is no time for everything. Last run shows which rows have gone unchecked: in the examples, the order history and the password reset email were last run a week before the rest, and the reset email has not been run in this round yet. A failed row, such as the card payment in the examples, is a bug to report with the steps already written.

Keeping the list healthy#

A regression list grows with every feature, and a list that is too long does not get run. Remove rows for features that are gone, merge rows that check the same thing, and add a row for every bug that reached your users. Rows that run on every release with the same steps are the first to automate, because a script repeats them exactly and never skips one. Regression testing for AI-generated code covers the automated version.

Regression testing vs sanity testing#

A sanity test looks at the one thing that changed in a build. A regression test looks at everything that was not meant to change. After a fix, run the rows in the sanity test template first, then this list. Afterwards, move the sanity row for the reported bug into this list. Smoke vs sanity vs regression testing follows one release through all three.

Questions#

What is a regression test case template?#

A sheet with one row per behaviour that must keep working, with its feature, preconditions, steps, expected result, priority, last-run date and status. The template on this page has nine columns and six filled rows.

How many regression tests do I need?#

Enough to cover what your users rely on most. Start with the High priority paths and add rows as bugs are found.

How often should regression tests run?#

Before every release, at least the High priority rows. If you release often, automate them.

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. Replace them with your own app's features and keep the columns.