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
- End-to-end testingEnd-to-end testing runs a scripted path through a whole application, from the interface to the database and back, to check that the parts work together the way a user would meet them.
- Synthetic monitoringSynthetic monitoring runs scripted checks against a live site on a schedule, from outside, to catch outages and slow pages before real visitors meet them.
- 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.
See it on your own site
Give an actor your URL. It opens a real browser, works through the site, and shows you every step it took.
Free to start, or watch a live demo.