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

Exploring development, test, and production environments

Spreadsheet programs that are stored locally don’t need environments. You can run them anywhere. What you are coding in a spreadsheet is what you are coding as you code it, what you are testing when you test it, and what you have coded when you are done for the moment Once we talk about storing information somewhere and having server-side code, we need to consider the path of that code from programmer to the live server. The classic way to think about that is some sort of promotion path. We’ll describe what this might look like in a few different ways; some of them may be more relevant to you than others.

Say, for example, that the application is a new and young website. It is small and fast enough that the code can run on the programmer’s computers which is a similar version of Linux to the eventual live server. Most continuous integration systems today can produce an artifact that is everything you need...