How I learned testing from mobile browsers
summary
Team consolidates many products into shared Android components, reusing telemetry and crash reporting and shrinking a portfolio that started as five and grows toward six or seven apps. Test team of about six to nine runs ~55 daily smoke tests (half automated), struggles with 450 BST tests weekly, and shifts automation from Robocop to Espresso UI. Builds include a quickly produced Fire TV browser that plays YouTube, a privacy-first Focus, and Firefox Preview (Phoenix) launched to Play Store; many experiments succeed, some require rewrites.
AI-written summary · about
chapters (22)
- 0:00Intro
- 2:15Why this talk
- 5:04Mobile browser history
- 11:23Timeline for adoption
- 13:30What testing is all about
- 18:10Testing process
- 24:59Private browsing
- 26:24Reference browser
- 26:56Unit test
- 27:29Firefox Lite
- 28:43New mentality
- 29:44No featured browser
- 31:19AB testing
- 32:36Alpha testing
- 34:02Firefox Inc
- 34:23Sharing tabs
- 35:11Future is bright
- 35:25Dont scare yourself
- 35:38Dont reinvent yourself
- 37:20The future
- 37:42Web Combat
- 38:04Outro
related talks
45mTesting the web without testers — success or failure
30mMobile Test Automation at the BBC: Then, Now and Next
31mEnd to end testing a world of web, mobile & desktop apps
53mTransforming testing methodologies: From manual to robust strategies
30mTesting & React Native"Lessons from the Battlefield"
01h 15mAgile Mobile Testing Workshop
40mLightning Talks
55mShifting the Testing Role Pendulum