Continuous Context Driven Test Improvement
Classical test process improvement is often not today’s best solution. With virtualization, SOA, web, cloud, mobile, and integration with social media, the way we develop, test, and manage has drastically changed. Jeroen explores why Agile, context-driven testing, SCRUM, continuous integration/development and DevOps require a flexible and pragmatic context-driven approach to test improvement. Context-driven test improvement is organized on two levels. [1] The improvement architecture level starts by clarifying the goal, scope, and context. This results in the improvement approach, a mixture of fixed- and free-format models and methods. The analysis of the collected information provides improvement suggestions that help achieve the “new” approach. [2] The improvement implementation level starts with transforming and prioritizing the improvement suggestions into tasks in the improvement backlog and fitting them into business-as-usual projects. Continuous improvement requires a continuous process that includes checking improvement results against the objectives—and, of course, new insights.
Test consultant for the Netherlands-based Polteq Test Services B.V. Jeroen Mengerink has performed multiple TPI assessments worldwide. His technical skills allow him to team with developers in testing websites, APIs, and web services. Jeroen performs both functional testing and performance testing. In addition to his work for clients, he is involved with test innovations in agile. Jeroen teaches the Certified Agile Tester course and courses on agile, SOA, and cloud; coauthored Testing Cloud Services; and blogs at jmengerink.wordpress.com. Follow him on Twitter @AngusVB.