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

Instead of talking about how to do test tooling and automation, this chapter covered the things a naive test toolsmith might discover in their first few years of work – at least, we hope they might discover them. As the saying goes, there is a difference between 10 years of experience and 1 year, repeated 10 times. Those problems include the depth of all that testing is (we tend to only automate part of the effort) and that defects tend to be unique, so repeated regression tests have only marginal value. We also discussed test maintenance as a hidden cost and how testing tools tend to either over-report or under-report defects.

Finally, we introduced a handful of patterns to, if not solve, at least decrease the pain of these problems.

While this chapter focused on exercising the software at the highest level, the next chapter will start at the lower level and move up. We call this programmer-facing, or the programmer’s approach view of testing.