Test with content stress
Long labels, empty lists, missing images and large values reveal layout weakness.
PROCESS / 04 / VERIFY
Polish the
edges.
Quality is usually lost at the edges: a small viewport, long title, slow request, keyboard user, unexpected CMS entry or browser difference. Verification deliberately visits those edges before users do.
Release confidence12 / 12 checks
✓320px layout✓Touch target✓Keyboard path✓Loading state✓Error state✓Long content✓Slow network✓Safari check✓Chrome check✓Focus states✓Contrast✓Regression
THE STANDARD
Do not test the screenshot. Test the product.
A confident release comes from checking behavior, content extremes, devices, browsers and accessibility states—not from one final visual review on the machine that built it.
VIEWPORTSmall → large
INPUTMouse + keyboard + touch
NETWORKFast + slow + failure
REGRESSIONShared components
WHAT GREAT LOOKS LIKE
Use multiple input methods
Keyboard and touch expose interaction assumptions mouse testing hides.
Check the failure path
Timeout, validation and API errors should give the user a clear recovery action.
Regression-test shared changes
One CSS or component change can affect many pages; verify the system, not only the edited screen.
PRACTICAL METHOD
Run viewport matrix
Check key breakpoints and the widths between them.
Run state matrix
Visit ready, loading, empty, error, success and disabled states.
Check accessibility
Verify focus order, contrast, labels and keyboard interaction.
Inspect performance
Look for layout shift, heavy media, blocking scripts and unnecessary motion.
Regression pass
Revisit connected pages and components before release.