Test the user path, not the implementation detail: navigate, act, assert and capture failure evidence.
The decision behind the technique
A successful build cannot catch clipped layouts, broken navigation or client-side state errors. Browser automation observes the rendered experience.
Test the user path, not the implementation detail: navigate, act, assert and capture failure evidence.
A practical step-by-step workflow
Use this sequence as a default, then tighten or expand it only when the evidence changes.
- Name one critical user journey
- Use roles and visible labels for actions
- Assert the resulting URL, text or control state
- Capture a screenshot only when visual evidence adds value
Failure boundary and finish line
Do not use brittle coordinates when the interface exposes semantic controls.
Finish when another person can reproduce the check against the exact final state.
Frequently asked questions
What should I do first?+
Name one critical user journey
What is the main failure mode?+
Do not use brittle coordinates when the interface exposes semantic controls.
OFFICIAL SOURCES
Verify against the source
Playwright documentationOpenAI MCP guidanceThis guide provides general information, not an OpenAI allowance promise or support decision. Your account and official pages govern actual usage, benefits and recovery times.