---
name: ui-ux-testing
description: Use when asked to evaluate a user interface's usability and user satisfaction — user testing, split testing, surveys, heatmaps, eye-tracking, expert review — as a set of techniques distinct from, but overlapping with, usability testing specifically (see usability-testing) and user-centred design methodology broadly (see user-centred-design).
---

# UI/UX Testing

UI/UX testing evaluates the usability, effectiveness, and user
satisfaction of a user interface or experience design — identifying pain
points and areas for improvement. See [[user-centred-design]] for
the broader design methodology this testing sits within, and
[[usability-testing]] for a deeper look at the observational
testing method specifically.

## Common approaches

- **User testing** — give users specific tasks and observe their actual
  interactions, behaviors, and feedback (see [[usability-testing]]
  for this method in depth).
- **Split testing / A/B testing** — show different design versions to
  separate user groups and compare which performs better on engagement,
  conversion, or another metric (see [[split-testing]],
  [[a-b-testing]]).
- **Surveys and questionnaires** — structured self-reported feedback on
  opinions, preferences, and improvement suggestions.
- **Heatmaps and click tracking** — visualize actual mouse movement,
  clicks, and scrolling to find usage patterns and struggle points
  quantitatively.
- **Eye-tracking** — specialized hardware/software tracking where
  attention actually goes, revealing what users notice (or miss)
  regardless of what they later report noticing.
- **Expert evaluation** — experienced UI/UX professionals review the
  design against industry practice and their own judgment, without
  needing live user sessions.

## Choosing among them

Quantitative methods (heatmaps, split testing, eye-tracking) reveal *what*
users actually do; qualitative methods (user testing, surveys, expert
review) reveal *why* — a mature UI/UX testing effort usually combines
both, since quantitative data alone can't explain the reason behind an
observed pattern, and qualitative feedback alone can't confirm how
widespread an issue actually is.

## Common pitfalls

- **Relying on a single method** — each surfaces a different kind of
  insight; heatmap data alone, for instance, shows *where* people click
  but not *why* they struggled there.
- **Trusting self-reported survey data over observed behavior** — what
  people say they do and what they actually do frequently diverge; direct
  observation (user testing, click tracking) is generally more reliable
  than self-report alone.
- **Skipping expert evaluation because user testing is available** — an
  expert review is fast, cheap, and catches known-pattern issues before
  investing in a full user-testing round.

## Learn more

- [[user-centred-design]] for the broader design methodology and research-method vocabulary this testing draws from.
- [[usability-testing]] for the observational user-testing method specifically.
- [[a-b-testing]], [[split-testing]] for the comparative-variant testing method.