What Pokémon GO has taught us about

testing & quality…

Intro

What team are you?

A Brief History

Niantic former Google Subsidiary

IngressIngress provided

the initial platform

Beta Release•Japan

•Aussie

•NZ

Then it went a tiny bit wrong…

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

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

Scaling Problems• Servers became overloaded• Bots spamming servers

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

Poorly Designed Features

•Removal of 3 paw prints•Battery saver mode

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

Battery DrainApp requires the screen to be on

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

GPS Weirdness• GPS inaccurate

• Unusable on some LG phones

Can’t Catch ‘Em All

• Device fragmentation• A/B testing effective• Very gradual release

Quality Continuum

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

Workshop Time…• What did this product teach us about testing?

• Everyone has an opinion!

• What would you have done differently?

Testing is about having a balanced approach…

So lets build one…

• HT to Dan North for his very useful ‘Testing Corners’

In the Blue Corner!

Types of testing and test ideas that (mostly) fit

How tools/techniques might assist

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

Go!