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

Putting Your Test Strategy Together

The previous chapter explored the puzzle pieces of testing. By the end, we had put them together, creating a potential dashboard to express the status of the software. Of course, that was only one potential dashboard among many, and our view of it was a conceptual one.

In this chapter, we will be looking at what we would consider good-enough software. When we have that, there is invariably some strategy already at play, which addresses some of the puzzle pieces that make up our testing process in some way. To be successful, we first need to figure out what is actually happening (the current state), as well as some ideal future state, and then address the gaps. That work needs to stand up to scrutiny. In other words, when a decision maker asks for ideas for how to move forward and wants to know “why,” “how,” and “when,” you need to be able to explain. They need to believe that their questions are answered...