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 standard data seed

Many business software systems are essentially some permanent data stores combined with a frontend. The data has to come from somewhere, such as an API that calls a database. For our purposes, the backend could be anything. It might be within our control (a database of our customers) or outside our control. For example, TweetDeck is a tool that helps people view and plan their X.com posts. (Formerly known as Twitter). The tool was originally created by an independent software company. The data for that tool is data from X.com.

Now think about trying to test the tool. You’d want to log in as a certain user, search for certain things, and confirm they show up on the user interface – but that is reliant on X having the right data. Terms such as 3 days ago would slowly age out; you wouldn’t be able to confirm them. If someone else was using the same account, they might corrupt the data and give you different search results.

Enter the standard...