I have seen Form Validation treated like a formality and like a real craft. One produces green statuses, the other produces confidence people can explain.
My checklist for Form Validation is not meant to turn testing into box-ticking. It exists so pressure does not erase the few important questions that protect field rules, recovery messaging, and preventing avoidable input pain. It gets expensive when the form rejects data correctly but explains it so poorly that people still cannot recover.
A good checklist keeps important risk visible when the room gets busy.
Before I Start
- Make the change area explicit
- Write down the most expensive failure in one sentence
- Confirm which users under time pressure should review open risk
- Choose the environment that will tell the truth fastest
During the Check
- Exercise the normal path that should protect field rules, recovery messaging, and preventing avoidable input pain
- Run an awkward-path example based on a payment form blocks progress because address formatting rules differ from what the UI suggests
- Watch for mismatches between visible success and hidden state
- Capture the one detail that will matter during sign-off later
Before I Close the Work
I finish by asking whether the evidence would still make sense to someone who was not present during testing. For this topic, the evidence I want usually looks like validation rules, inline feedback behavior, and examples of useful recovery guidance.
If the answer is yes, the checklist did its job. If the answer is no, I am not done yet. That is usually when confidence becomes visible enough to share, not just feel.