About the importance of automatic testing. From my talk held at Techdays by Init at November 27th 2013 in Stockholm, Sweden.

1. Always have everything
proven to work
November 27, 2013

2. Always have everything
proven to work
November 27, 2013

3. Always have everything
proven to work
November 27, 2013

4. Always have everything
proven to work
November 27, 2013

5. Always have everything
proven to work
November 27, 2013

6. Daniel Stenberg
●
Free Software
●
Network hacker
●
Embedded developer
●
Blabbermouth
Email:
Twitter:
Web:
Blog:
daniel@haxx.se
@bagder
daniel.haxx.se
daniel.haxx.se/blog

7. Agenda
●
●
●
●
Some trends in software and open source
backed by some data
How it looks like out there
What's important to take from this and what
it means for you and me
What the future holds

8. Feel free to interrupt
Object, ask, comment when you
feel like it.

9. What's happening now?
●
More of everything!

10. More devices with CPUs
●
Printers
●
TVs
●
Set­top boxes
●
Cars
●
Phones and tablets
●
Fridges, toasters and washing machines?
●
CPUs are cheap and capable enough
●
When I was young ...

11. Devices with CPUs
many
0
1993
2013

12. More CPUs with software
●
More full fledged CPUs
●
More Linux on your average CPU
●
●
More “common” software in
CPUs
37 billion ARM chips, “a million
PCs a day” ...

13. 32 bit processors sold
many
0
1993
2013

14. MIPS per die
many
0
1993
2013
http://www.r-bloggers.com/cpu-and-gpu-trends-over-time/

15. More software is open
source
●
Embedded OS: 2 to 1
●
Linux is defacto by chip vendors
●
Internet servers
●
Phones, Routers, Printers, Tvs and
cars

16. The future is open source
2009 ­ 26% believed more than 50%
of purchased software will be open
source within 5 years
2013 – 62% believes more than 50%
of purchased software will be open
source within 5 years
The 2013 Future of Open Source Survey Results – Black duck

17. Open source adoption
many
0
1993
2013

18. More open source
●
●
The term coined 1998
Number of projects virtually
doubled every year since

19. More open source
projects
many
0
1993
2013
http://dirkriehle.com/publications/2008-2/the-total-growth-of-open-source/

20. More open source
projects
http://dirkriehle.com/publications/2008-2/the-total-growth-of-open-source/

21. Software grows bigger
… and do so very fast

22. Bigger software: Linux
●
Unix 1.0 (1971) 10,000 lines
●
Linux 2.2 (1999): 2 million lines
●
Linux 2.6.0: 5 million lines
●
Linux 3.1: 15 million lines
●
Linux 3.12: 20 million lines
http://www.informationisbeautiful.net/visualizations/million-lines-of-code/

23. Other big software
●
Eclipse: 20 MLOC
●
Firefox: 9 MLOC
●
Android: 12 MLOC
●
Chrome: 7 MLOC
●
MySQL: 12 MLOC
●
GCC: 7 MLOC
●
PHP: 2 MLOC
●
glibc: 1 MLOC
●
Mac OS X “Tiger” : 85 MLOC
●
Windows Vista: 50 MLOC
●
Facebook: 61 MLOC

24. Lines of source code
many
0
1993
2013

25. More releases over time
●
●
Producers and users want tighter
release cycles
Switch hardware platform more
often
●
Use more commodity hardware
●
Increase code re­use

26. Release frequency
●
Linux kernel, every 9 weeks
●
Firefox, every 6 weeks
●
Chrome, every 6 weeks
“We're going to be getting new versions of Windows,
we're told, about every 12 to 18 months or so (the
number varies a bit depending on the source),
instead of every three to five years.”

27. New products per time
many
0
1993
2013

28. More
●
More devices with CPUs
●
More CPUs per device
●
More CPUs with software
●
More software is open source
●
Bigger software
●
More releases per time

29. Tomorrow...
Most of these trends are ongoing
with no signs of slowing down...

30. Coping
●
Make sure the code is always
good
●
Lower thresholds for releasing
●
Release even more often
●
Use and do open source

31. The 2013 Future of Open Source Survey Results – Black duck
The most important factor
for OSS adoption

32. Quality in an age of
speed
Non­stop automatic testing
Maintain quality
Be able to release often

33. Build on every commit

34. Test on
every
platform

35. Even cross­compiled
On a fully cross­compiled linux
distro, “make test” isn't straight
forward
Ptest – is one way to fix this. For
Yocto / OpenEmbedded

36. Daily snapshots and git
Kids today wants the latest now.
Give it to them or get replaced.

37. Let problems be known
●
Alert on IRC
●
Email the proper people
●
Show status on web sites

38. Fix problems at once
●
Be able to release soon
●
Users will get and use the latest
●
Others will push out their changes
soon and they need to be tested
and must not be blocked by your
bugs!

39. Summing up
●
●
●
●
●
Everything is happening more and faster
than ever
Software and open source are bigger
than before and are growing more
People want the latest immdiately after
changes have been pushed
Test your stuff to keep the users.
Automatic testing is the only viable
option.

40. Thank you!
Questions?
daniel.haxx.se