Mobile Test Automation at the BBC: Then, Now and Next
BBC Design & Engineering
Jitesh has over 15 years Test experience working with a wide variety of companies from Mobile manufactures to OS builders and app developers. He is currently the Principal Tester in the TV & Radio department working with the Mobile, TV and Web Platforms teams within the BBC to help identify their Test approaches and how the teams move to DevOps and beyond.
This is a case study of the Standard Media Playback team that builds the media playback capability for one of the UKs biggest VOD and AOD apps: iPlayer and BBC Sounds and how their test automation has evolved over the last 5 years. From rounds of manual regression testing then onto automated UI testing now to isolated code level tests and what’s next for the team. Then: How we started with UI automation to help us release quicker and what it actually gave us: fast checks of key user journeys but not an automated regression test suite that could help us release faster. Now: How we looked to push more of our testing down the stack into unit testing, but starting with building a team understanding of what unit tests actually are. How we broke down our system into interdependent components that could be tested in isolation and the architecture we used to push this further. All explained through a real life example of how we moved to the new ExoPlayer from google. Next: What new problems this approach has given us, how we plan tackle them and how we will bring this approach this to other teams across the BBC. Key takeaways - Testing: What has and hasn’t worked with our testing from manual to automated testing and everything in between - Pairing: How we collaboratively pair tester and developers to write code level tests - Team structure: How our teams are organised and why Risk Vs Value: How we balance the risk of not testing Vs value of testing it