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

Regulated testing

In many industries, a bug may be an inconvenience or perhaps delay something a user wants to do. Still, the results of such a bug would hardly be considered life and death. In some industries, however, death could be the consequence if a bug slips through. Think of the software that controls jet aircraft or marine shipping vessels. Think of medical devices. In financial software, if a bug were to be introduced, this could have catastrophic financial implications for an organization. These are areas where a much higher standard is applied and thus, regulations are in place to ensure that these organizations are offering the safest possible product with a minimal chance of failure.

Navigating regulatory requirements

Regulatory requirements typically spell out the types of testing needed, the documentation that must be written and followed, and the exact steps that must be followed to comply. The US Food and Drug Administration (FDA) uses IEC 62304 (https://www...