Zero to Test, How to Run Your First Beta Testing Program
summary
A small team builds and launches the FiscalNote iOS app after a 4 months push with one QA, one QA intern and a growing iOS dev team; beta testing surfaces usability tweaks and two classes of bugs: scraper-driven data quality failures and standard functional breaks, which get prioritized using the number of tickets and App Store rating KPI. For Real Talk beta users require daily content to retain teens. Methods combine analytics, follow-up calls, recorded sessions and session replay (FullStory) to turn observations into test plans.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:52Beta Testing
- 3:52Overview
- 5:19Fiscal Note
- 5:54Organizational Context
- 9:56Real Talk
- 12:17Three Steps
- 12:36Sell the idea
- 13:05Metrics
- 14:18Integration
- 14:40Decision Making
- 19:10KPIs
- 19:21Timeline
- 20:30Example Email
- 24:16Documenting Findings
- 31:00Recap
related talks
44mUser testing in production: how to run a public beta
46mBeta testing. Change course in flight
48mUser testing in production: how to run a public beta
42mNavigating Mobile App Testing and App Store Rejection
27mTESTING makes you a BETTER DEVELOPER
01h 02mKEYNOTE: Testing: The Next Generation
53mWhat Happens When Everyone is QA? And I Mean Everyone!
25mRapid prototype testing