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

The money problem

Imagine for a moment that you are leading a software organization that does not have any of this fancy-schmaltzy test tooling. The human test process is too slow; it is taking too long. Anytime you want to perform some testing, it takes you 2 weeks to sweat out a release. As a result, you’ve slowed down the release cadence, which means once it is time to get to regression testing, the code is in really bad shape.

Perhaps your organization isn’t like that and does better, and that’s fine. We haven’t found an organization we’ve worked with yet that can’t get to at least a 1-day human regression pass – but still, perhaps that is too infrequent. Perhaps you want results on every build.

So, you decide to start some sort of test tooling effort, perhaps through the user interface. Fantastic.

Who is going to do it?

If you have the testers do it, say, half the time, then it’ll take a very long time to make...