Mobile Testing Training That Actually Works
We run practical workshops twice a year because honestly, that's what works. You get hands-on time with real devices, actual bugs to find, and debugging tools you'll use on Monday morning. Our October 2025 cohort opens for registration in June.
Register Your Interest
What You'll Learn Over Six Weeks
We've been running this programme since 2022. Started with eight people in a conference room. Now we take twenty per cohort and the structure stays the same because it works – two evenings a week, real devices, actual problems to solve.
Dashiell Pemberton
Lead Instructor
Dashiell spent nine years at Nokia, then five more fixing payment apps at Barclays. He's good at explaining why things break and better at showing you how to catch them before users do.
Device Fragmentation Reality
We start here because it's where everyone gets surprised. You'll work with fifteen different Android devices in one session and watch the same code produce completely different results. Then we show you how to manage it.
Network Conditions & Performance
Apps don't just run on WiFi in London. You'll simulate 3G in rural Scotland, packet loss on the Tube, and connection switches between cell towers. These scenarios break more apps than crashes do.
Memory Management & Crashes
This is where we dig into why apps close unexpectedly. You learn to read memory dumps, spot leaks before they become problems, and understand what happens when Android decides your app needs to go.
Debugging Tools Deep Dive
Android Studio has about forty debugging features. You'll use maybe eight of them regularly. We focus on those eight – the ones that actually save you time when production is broken at 4pm on Friday.
Automated Testing Foundations
We're not trying to make you automation experts in one module. But you need to understand Espresso basics and when automation makes sense versus when manual testing is faster. Real-world balance matters.
Release Process & Production Issues
Final week covers what happens after you ship. Monitoring tools, crash reporting setup, beta testing programmes, and how to handle that moment when analytics show something's very wrong with the latest release.
Where This Actually Helps
These skills show up in different ways depending on where you work. Some people use them daily, others keep them ready for when things go sideways. Either way, they're useful to have.
Catch Issues Earlier
You'll spot problems during development instead of after release. Saves time, reduces stress, makes the whole team's job easier when bugs don't make it to production.
Debug Faster
When something breaks, you know where to look and which tools to use. What used to take hours might take twenty minutes. That matters when deadlines are tight.
Understand Performance
You learn to read profiling data and spot performance bottlenecks. Battery drain, slow load times, memory issues – you'll know how to measure and improve them.
"I'd been doing web testing for three years but mobile was different enough to be frustrating. This programme filled in all the gaps. Now when developers ask me to check something on Android, I know exactly what to test and why. Worth every Tuesday and Thursday evening."