UX regression testing
Also called experience regression testing, continuous UX testing
UX regression testing checks, after every change, that the flows users depend on still work and still make sense, not only that the code still passes.
A unit or end-to-end test asserts exactly what it was written to assert. It passes when a button moves below the fold, when a label changes to something nobody understands, or when a new modal covers the checkout on mobile.
A UX regression test is written as a requirement in plain language, "a new user can sign up and reach the dashboard", and judged the way a user would meet it. It runs on a schedule or on every deploy, so a change that breaks the experience is caught before customers report it.
Where Stunt Double fits
Checklists are UX regression tests. Each requirement is checked by an actor in a real browser on every deploy, pull request or schedule, with a screenshot and the reasoning behind each pass or fail.
Related terms
- AI user testingAI user testing sends AI agents with defined personas through a product in place of recruited participants, and reports what each one did and where it got stuck.
- Usability testingUsability testing watches people attempt real tasks in a product to find where they hesitate, make mistakes or give up.
- Browser agentA browser agent is an AI model that operates a web browser: it reads the page, decides on an action such as a click or a keystroke, performs it, and repeats until the task is done.