Book Image

Software Testing Strategies

By : Matthew Heusser, Michael Larsen
Book Image

Software Testing Strategies

By: Matthew Heusser, Michael Larsen

Overview of this book

Software Testing Strategies covers a wide range of topics in the field of software testing, providing practical insights and strategies for professionals at every level. With equal emphasis on theoretical knowledge and practical application, this book is a valuable resource for programmers, testers, and anyone involved in software development. The first part delves into the fundamentals of software testing, teaching you about test design, tooling, and automation. The chapters help you get to grips with specialized testing areas, including security, internationalization, accessibility, and performance. The second part focuses on the integration of testing into the broader software delivery process, exploring different delivery models and puzzle pieces contributing to effective testing. You’ll discover how to craft your own test strategies and learn about lean approaches to software testing for optimizing processes. The final part goes beyond technicalities, addressing the broader context of testing. The chapters cover case studies, experience reports, and testing responsibilities, and discuss the philosophy and ethics of software testing. By the end of this book, you’ll be equipped to elevate your testing game and ensure software quality, and have an indispensable guide to the ever-evolving landscape of software quality assurance.
Table of Contents (22 chapters)
1
Part 1:The Practice of Software Testing
9
Part 2:Testing and Software Delivery
14
Part 3:Practicing Politics

Context-driven testing and the other schools

In Chapter 8, we introduced the idea of Agile software development, which is typically contrasted with Waterfall development. We also introduced context-driven testing, without providing much contrast, except as it was understood in the Waterfall and V-Model.

There are, however, various ways of thinking about the purpose and role of testing. One we’ll dive into in some depth later is the idea of process-oriented testing, which can be summarized as “plan your work; work your plan.” That sounds sensible, on the surface. Yet testing exists because people made a mistake; something unplanned happened. In our experience, many of the best test ideas are unplanned and emergent. Context-driven thinking allows for the possibility of learning from the process and coming up with new ideas at the moment. That allows for planning, but much less of a prescriptive, pre-defined process.

Brett Pettichord, a co-creator of the context...