1. What Pokémon GO has
taught us about
testing & quality…

2. Intro
What team are you?

3. A Brief History
Niantic former
Google Subsidiary

4. Ingress
Ingress
provided
the
initial
platform

5. Beta Release
•Japan
•Aussie
•NZ

6. Then it went a tiny
bit wrong…

7. App Freezing
• App had
to be
rebooted
• Lost
Pokemon
and
items

8. No Crashes Rule
• Crash
and you
burn
• Or not
• Kept on
playing

9. Scaling Problems
• Servers
became
overloaded
• Bots
spamming
servers

10. Keep On Keeping On
• Hitting new
markets
over
scalability
• Timing is a
quality
criteria

11. Poorly Designed
Features
•Removal
of 3 paw
prints
•Battery
saver
mode

12. Features != Quality
•Focus on
your core
idea
•Do few
things
well

13. Battery Drain
App
requires
the
screen
to be on

14. Quality is composite
• Wider
system
• Remove &
add
• Compelling
idea

15. GPS Weirdness
• GPS
inaccurate
• Unusable
on some LG
phones

16. Can’t Catch ‘Em All
• Device fragmentation
• A/B testing effective
• Very gradual release

17. Quality Continuum
• Quality is on a multi
dimensional continuum
• Great brand & idea provides
elasticity

18. Workshop Time…
• What did this
product teach
us about
testing?
• Everyone has an
opinion!
• What would you
have done
differently?

19. Testing is about having
a balanced approach…

20. So lets build one…
• HT to Dan
North for
his very
useful
‘Testing
Corners’

21. In the Blue Corner!

22. Types of testing and
test ideas that
(mostly) fit

23. How tools/techniques
might assist

24. Get Ready…
• Groups!
Peeps you
don’t know
if you can.
• Post Its,
Pens, Paper!
• 15-20 mins
• Reflect…

25. Go!