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

What are we doing now?

The Oxford English Dictionary defines strategy as “a plan of action or policy designed to achieve a major or overall aim.”

When we talk about strategy, we mean the plan of action (plus policies) to achieve an aim. In our case, the plan of action will cover what we will do (and how we will do it) when testing software, with the goal of providing-makers with information about management’s intent, so that the technical team, and even the person doing the testing, can make decisions on how to move forward. In other words, part of the strategy might be to push the decision-making activities into the team. This eliminates the need to wait for someone external to decide what to do when a bug is found. The more we can push decisions into real time and eliminate waiting, the more we’ll improve system performance. When we write “decision making”, that doesn’t have to be a big thing; it doesn’t need to be deciding...