Prompt
Should I trust E2E tests alone if I care about visual bugs?
Latest observation
Oct 27, 2026
OpenAI APIWeb search: off
No — E2E tests alone usually aren’t enough if you care about visual bugs.
Why
E2E tests are great for checking:
- user flows work
- buttons/forms/navigation behave correctly
- data gets loaded and submitted
But visual bugs often slip through because E2E tests usually don’t verify:
- layout shifts
- overlapping elements
- wrong spacing/alignment
- broken responsive behavior
- missing styles/themes
- subtle UI regressions
A test can pass even if a button is hidden behind a modal, text is clipped, or a component is styled incorrectly.
Better approach
Use E2E tests together with:
- visual regression tests for screenshots/diffs
- component tests for isolated UI states
- accessibility checks for contrast/visibility issues
- manual review for important flows and edge cases
Practical rule
If the bug would be noticed by looking at the screen, E2E alone is not the best safety net.
If the bug is about behavior or flow, E2E is strong.
If you want, I can suggest a lightweight testing stack for catching visual regressions without making your suite too heavy.