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

Flow

Imagine you’re in an engineering plant. Raw materials come into the plant, where they are painted, assembled, repainted, have a QA inspection, are loaded into trucks, and hauled away. The workers can offload 1,000 widgets per hour into the staging area; initial painting is 750 widgets per hour, assembly is 500, repainting is 750, and the team can inspect 1,000 widgets per hour. What is the net output of the factory?

It doesn’t take a wizard to figure out that the factory will produce an output of 500 widgets per hour. Performance improvements regarding the repainting or inspection team are a total waste of time. It would be better if those teams decreased staff, moving them to help with the assembly process. Eli Goldratt’s theory of constraints provides some ideas to help us improve performance in such a factory. For example, we want to keep the assembly team working all the time; we might build up a little parts inventory in front of them in case they...