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

DevOps, Platform Engineering, SRE

By the early 2000s, most new software development done was on websites, or else on company data centers. In both of those worlds, there were two sides: the developers who created changes, and the operations staff whose job was to keep the system stable. As the easiest way to keep systems stable is to prevent change, the two were often at odds with each other. The DevOps movement tried to align the incentives between the two, by getting operations on the same side as the developers, using the same programming languages, tools, and techniques, and often applying programming acumen to operations problems.

By 2011, continuous delivery was presented as a platonic ideal for software – eliminate regression testing by pushing just what changed and nothing else, all the time! Yet at the same time, software came from a single-build tradition that went all the way back to Windows and DOS applications.

In many cases, DevOps/Platform Engineering includes...