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

A few thoughts to leave with

Gerald M. Weinberg used to come up with quick, easy, pithy sayings to remember the key points of his work. We may not be Jerry Weinberg, but we do recognize that a few of our ideas compress well into his format. We have collected a few of our favorites here:

  • The consultant’s gambit: There are probably obvious problems insiders can’t see because of company culture that outsiders will see.
  • The maxim of documented testing: At the end of every human-run, pre-designed, documented test is a hidden expected result: … and nothing else odd happens.
  • The first corollary: This assumption is particularly difficult to automate.
  • The second corollary: If you try to automate the search for the hidden expected result, you’ll get a whole lot of false errors.
  • The maxim of test automation: Even if a test could be automated, the second time it runs, it fails to be test automation and becomes change detection.
  • The exception...