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

Human Or Tooling—is it either/or?

When people talk about test automation, in particular customer-facing test automation, they likely mean a few specific things:

  • When I, as a technical person, click a button:
    • This may cause The building and deployment of the software to occur
    • This may cause a refresh of the test code from version control
  • The tests run against the build
  • The tests report the status of the software

The term test automation, examined this way, might be more accurately described as unattended test execution, evaluation, and reporting. When people talk this way, they usually don’t mean automated test design or selection. Likewise, the reporting is rarely good enough to give to programmers to fix. Instead, failing tests need to be investigated and adjusted based on the changing software. Sometimes the test code needs to be updated to match the changed production code and sometimes the test code is flaky (more on this in Chapter 11). Even...