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

Technical requirements

This chapter will refer to the idea of tracking our work and collecting information about that work. How you do that, we don’t care. A particularly high-functioning team with high trust might just put sticky notes on a board, use a marker, and use running, tested features as the primary measure of progress. At the time of writing, it is far more common to use a tool such as Jira, Trello, or Microsoft Teams to track work and then perhaps export the data into a spreadsheet to gather the metrics. This book will provide solutions for both extremes and most people in the middle. Having access to these tools so that you can gather the data yourself will allow you to internalize the lessons of this chapter, and it is likely to provide key information to decision-makers. Having access to those tools and reviewing them could help demonstrate the validity of our ideas. On the other hand, a lack of these tools may help you realize what you are missing.

A few years...