Bridging the gap between UX and QA through design systems
summary
Design systems deliver a living component library that becomes one source of truth, cutting hundreds of bespoke buttons down to a handful (he cites “five buttons, one calendar”) so designs match code and QA tests. Uses atomic components, versioned releases, and a recommended centralized model with devs, QA and designers contributing. Builds include documented components, code snippets and sandboxes; testing uses unit tests (Mocha/Jasmine), functional (Nightwatch/Casper), visual regression (Applitools/Percy) and automated a11y checks to keep it robust.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:23Design consistency
- 3:53Design systems
- 5:22Design system overview
- 10:51Designing a design system
- 13:37Research
- 15:26Design
- 17:39Selfcontained
- 19:16Robust
- 19:42Adoption
- 22:11Roadmap
related talks
27mFoundations of Design Systems
46mBuilding & Managing Design Systems
57mBulletproof development with design systems
18mDesign Systems in Practice
15mHoly War between Designers & Developers
20mDesign Systems for the Rest of Us
36mUX designers /developers collaboration anti patterns
25mIntegrating UX and DX