Field guide · 7 min
How to QA a SaaS signup flow
A practical method for testing the states between landing page and first useful product moment.
01
Start with the promise
A signup flow is not successful because an account row exists. It is successful when the person understands what happened, reaches the intended product state, and can recover from predictable mistakes.
- ●What must a new user know before starting?
- ●Which inputs block progress?
- ●What is the first useful state after signup?
- ●How can a user recover from interruption?
02
Vary one condition at a time
Test each required field independently before combining invalid inputs. This produces precise failures and reveals whether validation is attached to the right control.
- ●All fields empty
- ●Each required field omitted in turn
- ●Invalid and boundary formats
- ●Duplicate account details
- ●Browser back and refresh during the flow
03
Preserve the evidence
Record the starting state, action sequence, visible outcome, expected behavior, and environment. A result without a reproducible path is an observation, not yet a useful bug report.