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.

1. How to test the
Internet Of Things
German Testing Night Munich, 28.02.2013
Henning Böger
https://twitter.com/HenningBoeger
henning.boeger@gmail.com
© Henning Böger 2013

2. Internet Of Things (IoT)
Relevant for me?
If yes: How do I test it?
© Henning Böger 2013

3. Internet Of Things
{
Smart
Things
Connected
© Henning Böger 2013

4. Example: Smart Home
© Henning Böger 2013

5. You want more than just lamp on/off
© Henning Böger 2013

6. Lots of interconnected systems
Not under your control
© Henning Böger 2013

7. Internet Of Things will be
everywhere. Likely in your field too.
Smart Home Connected Car
Smart City
Connected Body
And: Agriculture, Logistics, Construction, Retail, ...
© Henning Böger 2013

8. How do you test the zoo?
Classic integration test What about
Rest Of World?
© Henning Böger 2013

9. Your customers will hate you if
you use classic test approach
Where bugs are found
Unit test Unit test
Component test
Component test
Integration &
acceptance test
Integration &
acceptance test
By customer
{
By customer
Classic system Internet Of Things
system
© Henning Böger 2013

10. 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

11. 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

12. 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.
© Henning Böger 2013