adversarial-ux-test

Adversarial UX testing identifies real friction by roleplaying a resistant persona attempting the core workflow end-to-end, capturing evidence of usability issues like onboarding validation failures. It separates genuine product friction from persona complaints to expose real user experience problems.

Adversarial UX testing evaluates error recovery and accessibility by having a tech-resistant persona navigate the core workflow. It checks readability, navigation, and terminology, capturing screenshots and verifying JS console errors to generate actionable UX tickets for real issues found.

Apply a pragmatism filter to classify usability testing complaints into RED, GREEN, or WHITE categories. Convert only RED and GREEN findings into a maximum of 10 actionable UX tickets, skipping WHITE noise complaints to ensure the ticketing output remains focused on real product issues.

Yes, adversarial UX testing requires persona creation or selection to evaluate navigation and terminology usability. You can specify a grumpy persona to browse your staging app, attempt core tasks, and capture evidence of friction during structured browsing and task execution.

Adversarial persona testing finds genuine friction that standard product feedback and technical QA miss. By intentionally roleplaying a difficult, low-comfort user who hates technology, it breaks the core workflow and applies a pragmatism filter to separate real issues from subjective noise.