Operations · Systems · Automation  /  Process first. Then automation.Explore free sessions ↗
Discuss Your Workflow ↗
DESIGN PREVIEW · Proposed offers & sample work · Dates / fees awaiting approval · No live payments
Automation

Workflow test checklist

Test more than the happy path before handing a flow over.

EDITABLE GUIDEAutomation

What this guide covers

Test more than the happy path before handing a flow over.

Sections

  1. Normal input. Does one valid request produce one intended result?
  2. Missing input. Does the process stop and explain what is missing?
  3. Duplicates. Does repeating the same request avoid duplicate actions?
  4. Approval. Can an unapproved request trigger a consequential action? It should not.
  5. Service failure. Is a failure visible, recoverable and assigned to an owner?
  6. Access boundary. Can a user access only the information and actions they are permitted to use?

Worked example

Record: case ID, input, expected behaviour, observation, pass/fail, reviewer and date. This checklist is not a security certification.

How to use it

Download the editable file, fill it in with a real task from your own work and revise it once you have tried the process. The guide is meant to be used, not filed.

This guide is educational material. It is not legal, security or compliance advice. If your work touches regulated data, involve the right professional before automating.
Related

More in Automation

All resources
Editable checklist

Automation Readiness Checklist

Check the rules, data, access and exceptions before you build.

Read the guide

Want help
filling it in?

Bring the guide and your task to a focused session. We’ll work through it together.