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

Recipes – how to do hard things

One client we worked with had test cases stored in a test case management system. With that software, you could pick one project, get a list of test cases, and then get details about those test cases. For any release, you could create a “test run,” and for every test run, you could mark the cases as passed or failed. By the time Matt arrived at the client, they were using an ancient client/server system whose version had just run out of support. The next version of the software would require a budget to upgrade. The operating system of the server was too old, so that would need to be upgraded, and the hardware was underpowered and out of date. Management performed a bulk export to Excel, threw the old test cases onto a network drive, and threw the test case management system away.

Nobody noticed.

To say that no one noticed might be a slight exaggeration. From time to time, someone on the team would be testing a particularly...