Leveraging Automated Testing Data to Enhance User Experience
summary
Argues that automated testing data directly improves UX by surfacing real failures and behavior patterns: unit tests reveal component logic issues, integration tests show API mismatches, and end-to-end runs catch 404s, load-time spikes and user flow interruptions. Shows practical wins: adding data-test-id attributes in early Figma prototypes, running cross-browser suites with Playwright visual testing, piping results into Azure App Insights and data aggregators, and trimming maintenance on sprawling suites (author cites pain of ~100k tests) to prioritize the flows that actually matter.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 1:19What is QA and its importance
- 2:47Collaboration between UX and QA
- 7:12Automated testing in UX
- 10:04Types of testing data
- 12:39Key tools for QA and testing
- 13:20Why Playwright for robust testing
- 15:05Early collaboration and design systems
- 16:31Q&A session
related talks
30mElevating User Experience Through Effective Testing Strategies
20mPanel Discussion on Testing
51mRedefining test automation
32mUX !=UI: Testing UI and UX
42mIntroducing the benefits of the testing diamond
39mAccess Points for Testing: From Human Opportunities to Digital Techniques
32mWhy testing is a developer's problem
57mAdvanced Testing Techniques: Tips from the trenches