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

Strategy – what are our risks and priorities?

If you have gotten this far, then you recognize that there is an essentially infinite number of possible tests to run. Breaking the software into features, assigning a minimal test-effort value for the feature, making a list of the full end-to-end customer journeys… all of these things make the effort manageable. The 5-minute test plan and iterating around the product seem easy, but what do we do when there is just too much to test and some very limited time? One technique we’d like to mention here is RCRCRC.

Karen N. Johnson, a friend of ours who we have worked with, proposed a mnemonic – a memory device – for regression testing. She called it RCRCRC (http://karennicolejohnson.com/2009/11/a-heuristic-for-regression-testing/). This involves coming up with test ideas with short notice. Here are the letters defined, in her words:

  • Recent: New features and new areas of code are more vulnerable
  • ...