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

Summary

The goal of this chapter was to enable you to look at your software process in an entirely different way, to see every day easy choices as introducing waste. With a little work, you can even start to see not just the waste and bottlenecks but the impact of those bottlenecks on the delivery process. This allows you to suggest concrete changes to help the organization go faster.

To do that, we first explained the history of lean, then tried to explain and adapt it for software with the concepts of the seven wastes, flow-based thinking, CD, and one-piece flow. We ended up with an idealized way to deliver software that few of our customers accomplish. Even the ones writing blog posts about CD fail to achieve that ideal – but most of us can benefit from moving in that direction.

That said, there is a particular reading of one-piece flow, and thought about testing, that we’d like to mention here. Many people have told us that testing is too late, that what we...