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

Building a risk mitigation team

You might be familiar with the old question, “Why didn’t testing find that bug?” It sounds innocent enough. Usually, it is in fact an assertion that testing should have found that bug. The short reason is that someone made a mistake, and people do make mistakes. For the most part, testing exists because people make mistakes. Testing mitigates, or reduces, the risk of a mistake. There are other factors; testers can think of things no one else thought of or provide other quality-related information such as a feature idea. Still, for the most part, we can think of the defects created, and the tests run as two overlapping circles. Defects that exist outside that circle need to be caught by something else, or else they will escape to the customer.

Here’s a simple exercise.

Write down on a piece of paper everything you might do to reduce risk in a project – that is, every type of activity your company runs to catch...