Reports of the Death of Testing Have Been Greatly Exaggerated
- 1. W18 Special Topics 5/1/2013 3:00:00 PM Reports of the Death of Testing Have Been Greatly Exaggerated Presented by: Ruud Teunissen Polteq Test Services BV Brought to you by: 340 Corporate Way, Suite 300, Orange Park, FL 32073 888-268-8770 ∙ 904-278-0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com
- 2. Ruud Teunissen An international test consultant at Polteq Test Services BV, Ruud Teunissen has performed several test functions in a number of IT projects: tester, test specialist, test consultant, and test manager. Ruud participated in the development of the structured testing methodology TMap® - Test Management Approach. Together with Martin Pol and Erik van Veenendaal, Ruud is coauthor of several books on structured testing, including Software Testing: A Guide to the TMap® Approach.
- 3. Reports of the Death of Testing Have Been Highly Exaggerated Ruud Teunissen Polteq Test Services BV The Netherlands Reports of the Death of Testing Have Been Highly Exaggerated Have you heard? It’s all over the social media. We are the “last generation of testers.” Testing is dead. No more classical testing—too much inflexible process. Context driven? That is a code phrase for do whatever. Agility? Developers do testing, and testers become developers. DevOps? Development and operations join forces—and test is not in the picture. And, companies don’t test anymore—they outsource. Ruud Teunissen believes we must save the indispensable craft of testing. Non-functional tests require special skills; new paradigms like cloud and mobile must be explored and tested; Enterprise-to-enterprise integration tests become more vital as systems grow larger and more complex. And who’s going to do that testing? Testing skills are needed to work effectively and efficiently in these new contexts. Learn to save the testing skills within your organization and do what you’ve always done best—save the day by preventing defects from going live. 2 1
- 4. Let’s have a look at the evolution of testing Pioneering Optimizing Structuur Unstructured Undisciplined Flexible Specialization Structured Disciplined Inflexible Structuring Once Now 3 Once upon a time testing was pioneering • Unknown, no buy-in, no budget, no process, no tools • Fully integrated in the development process – Generalists, joined effort – Prototype, exploratory driven – No dedicated testing staff • Struggling to get involved • Not a partner, no influence • Discussing risks not done • Only in emergencies 4 2
- 5. Because bugs lead to disasters … ” If debugging is the process of removing bugs, then programming must be the process of putting them in. „ Edsger Dijkstra 3
- 6. … we started specializing and structuring • Structuring the process • Standardization (Books) • Defining the test function – Certification – Independent • Functionality and non-functionality • Test automation • Test process improvement models – TPI, TMM, TMMi, TOM, TIM, TSM, … 7 Testing! • Dedicated (trained) staff • Recognized as a function • Test competence center • Master test planning • Risk based coverage • (Early) involvement • Independent testing 8 4
- 7. Testing? • Becoming a referee • Process Improvement freaks • Inflexible • Metrics mania • Spreadsheet management • Complaining and blaming • Tunnel vision 9 Changing context Technology push Efficiency push 10 5
- 8. Changing context Technology push • Architecture – – – – SOA Virtualization Web technology Devices • Cloud • SoLoMo • Integration 11 Changing context Efficiency push • • • • • • • Outsourcing Package software Cloud Agile, Scrum DevOps Continuous delivery Collaboration 12 6
- 9. Testing is challenged Keynote EuroSTAR 2011 Pursuing quality? (you won’t get there by testing) James Whittaker Engineering Director, Google TestNet (Dutch SIGIST) Model Driven Development, the end of the test profession? Johan den Haan CTO, Mendix 13 Testing is challenged xxxxxxxxxxxxxxxxxxxxx Process = out Certification = wrong 14 7
- 10. Testing is challenged • Context Driven – Right solution, practice, coverage, cooperation, skills Major factor: PEOPLE! 15 Testing is challenged • Context Driven – – – – Right solution, practice, coverage, cooperation, skills Exploratory Session based Rapid Context driven = less 16 8
- 11. Testing is challenged Tester = ? 17 Testing is challenged Tester = agilist 18 9
- 12. Offshoring, outsourcing Package software Cloud computing 19 20 10
- 13. • Changing role • Distributed – Business/RQMS – Development – Operations 21 • Changing role • Distributed • Technical – – – – Automation Cloud SoLoMo Security 22 11
- 14. • Changing role • Distributed • Technical • Programming – Automation – Development 23 • Changing role • • • • Distributed Technical Programming Social – Team player – Communication 24 12
- 15. Cooperate Facilitate Innovate Optimize 25 About the speaker Ruud Teunissen Polteq Test Services, The Netherlands ruud.teunissen@polteq.com - http://www.polteq.com Ruud Teunissen is best described as a passionate software tester. Throughout his career he has played almost any possible role in testing (tester, test manager, test trainer, coach, sales, manager, test consultant, …) in a variety of environments and companies. Ruud is coauthor of several books on structured testing, including Software Testing: A Guide to the TMap® Approach. Currently he is senior test consultant with Polteq Test Services BV and focuses on test improvement and management in any context. Ruud is frequently invited to speak at conferences. Within Polteq, Ruud is responsible for TI4Automation, the approach for successful implementation and improvement of test automation based on hands-on experiences and good practices. 26 13