App Engineers and QA Team Tackle Improving Debugging Features!
summary
A joint app-engineer and QA improvement team ran a QA survey to score requested debug features by impact and development difficulty, then implemented high-payoff items: server flags and backend endpoints to expose user and vehicle IDs for easy copy-paste, a unified debug UI for Android and iOS, documentation and emulator setup for QA, and adoption of the Voyager device-mirroring/recording tool. These changes reduced regression testing effort from about 35 person-days and 15 tickets per run to far fewer tickets, though some features are still in progress.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:11Old team structure drawbacks
- 4:15New team structure benefits
- 5:40QA regression testing challenges
- 7:06Gathering QA feature requests
- 9:19Prioritizing QA features
- 11:04Introducing Voyager
- 12:28Debug screen improvements
- 14:55Debugging feature results
- 16:23Future outlook
- 17:45Summary
related talks
53mWhat Happens When Everyone is QA? And I Mean Everyone!
13mDebugging debugging; why we must approach debugging differently
23mWhy testing is also a developer's problem
36mDAAS: Debugging as a skill!
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
43mDebug Better in Android Studio
49mOptimizing QA Flow to Minimize Time to Release While Meeting Quality Standards
50mAn Exploration of Debugging Techniques and Tools