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

Today’s strategy versus tomorrow’s goals

Starting with the lean test canvas, you might end up with a list of activities people do in various roles and the times they do them. That is not bad. The visuals from this chapter and the previous one try to tie that back to risk and priority. Hopefully, you can find some way to get started, by adding a shared spreadsheet for emergent risk, taking a long list of test cases and turning them into a summary or creating a mind map. One company we worked with started with a list of perhaps 12 major pieces of functionality in the application, each with 5 to 10 sub-items. At the start, they simply had to identify which team was responsible for what parts of the application. With over 100 full-time staff on the project, the process took nearly three months. The last month ended with senior executives hounding teams at the end to take responsibility for the unclaimed parts of the application. Once that was done, management had each team...