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

Influencing change

We can argue that testing is “just” a technical investigation to uncover quality-related information. That’s fine, as far as it goes — but it doesn’t go very far. If the test effort discovers problems, and those problems are well documented yet never read… nothing happens. The real value to the business of the test effort is zero. Perhaps the company gets lucky, and there are no “showstopper bugs,” and the customers don’t care. In that case, a rational executive should eliminate the testing budget. Or perhaps the company goes out of business.

Most of us don’t have that problem, but we may have a problem where testing finds defects, and some get fixed, but not enough. Just as bad, the programmers don’t learn from their mistakes, and keep creating the same kind of bugs, over and over again. This creates drag on the team. Some testers find this comforting as they will always have a job....