how to test the internet of things
DESCRIPTION
Internet Of Things systems are different to classic systems in a known environment. Things are messy and you can't control anything. Your test methods need to change accordingly.TRANSCRIPT
© Henning Böger 2013
How to test the
Internet Of Things
German Testing Night Munich, 28.02.2013
Henning Böger https://twitter.com/HenningBoeger
© Henning Böger 2013
Internet Of Things (IoT)
Relevant for me? If yes: How do I test it?
© Henning Böger 2013
Internet Of Things
Things { Smart
Connected
© Henning Böger 2013
Example: Smart Home
© Henning Böger 2013
You want more than just lamp on/off
© Henning Böger 2013
Lots of interconnected systems
Not under your control
© Henning Böger 2013
Internet Of Things will be
everywhere. Likely in your field too.
Connected Car
Connected Body Smart City
And: Agriculture, Logistics, Construction, Retail, ...
Smart Home
© Henning Böger 2013
How do you test the zoo?
Classic integration test What about Rest Of World?
© Henning Böger 2013
Your customers will hate you if
you use classic test approach
Integration & acceptance test
By customer
Where bugs are found
Unit test
Component test
Classic system
Integration & acceptance test
By customer
Unit test
Component test
Internet Of Things system
{
© Henning Böger 2013
New solutions needed
• „Test by Customer“ is a First Class Citizen
• Tailor your process accordingly (Ship Early, Friendly Users, ...)
• Tailor your toolchain accordingly (user feedback, remote debugging, zero turnaround)
• <Your idea here>
© Henning Böger 2013
Optimize turnaround times
Turnaround times: • Exception on device until issue tracker: 1 sec • Establish remote debugging session: 1 sec • Build new firmware with bugfix: 5 sec • Remote firmware update: 10 sec • Rollout bugfix release: 10 min
© Henning Böger 2013
Wrap Up
Internet Of Things will pervade more application domains. Likely yours, too.
Your classic integration test is not
sufficient.
You need to treat „Test by Customer“ as a First Class Citizen.