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 minefield regression problem

Again, we are talking about a certain type of test automation, something we call click-click-click, inspect testing. In this vision, we take the user journey and have a computer go through it, looking for problems along the way. Unit and programmer tests can do this too. The important thing is that the test doesn’t have much randomization in it. Model-driven tests and other approaches have these problems to a much smaller extent, but there is a reason those approaches don’t ever seem to take off or survive.

For now, someone is writing what they call a test. The implementation doesn’t matter. Let’s say it is an eCommerce application, so we have a half dozen “tests” that exercise the application, creating a profile, searching, finding a product, adding it to the cart, and going through the motions of checkout.

Note something about that search test – it doesn’t add any value as it is created...