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

Pair and tri-programming

Extreme Programming (XP) introduced pair programming, which has faced significant resistance as the implication is programmers will move half as fast. Honestly, we think that’s silly. One dirty little secret of computer programming is that most programmers do not and cannot seem to work a full 8-hour day. Programmers check emails, Slack, message boards, social media, and all other kinds of distractions. There’s coffee to get (and re-get), and, for the ones who work from home, laundry to do and sandwiches to make. The little secret of pair programming is that both people need to be on-task. If a typical programmer spends only half the day in deep work, moving to pairs can double the deep work time. That is no significant loss of forward velocity. The second set of eyes and ears can catch problems the first would not have seen.

Ping-pong is a common way to do test-driven development, where one person takes the keyboard and writes a test, and...