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

Technical requirements

Test data needs to be saved, archived, loaded, version controlled, and so on. That, in a way, makes it very much like code. Our goal with this chapter is to aid the communication between programmers and less technical staff. Specifically, a tester who does not program might be able to create technical requirements for the test data that a product owner could prioritize as a feature for ongoing development. You’ll also learn how to articulate the cost in terms of time investment if those tools don’t exist. Programmers who read this chapter will understand the ideas and immediately be able to implement them.

The solutions in the chapter will tend to be high-level, programming-language-agnostic concepts. So, no specific programming language is required. An understanding of databases and SQL will be helpful. Teams that use key/value pairs and NoSQL databases will also be able to benefit from this chapter.