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

Extreme Programming (XP)

Extreme Programming, or XP, started out as essentially a thought experiment of what would happen if good things were taken beyond their usual limits. One term for this is to crank the dials to 11, which comes from attempting to turn speakers beyond their regular limits on a one-to-ten scale. Here are a few questions XP asks:

  • If shorter delivery timeframes (mini-waterfalls) are good, what if we just organize the work into iterations of two weeks or less, and deploy at least every three iterations? (This goal was later shortened to every iteration.)
  • If working closely with customers is good, how about we have an on-site customer as a team member? (For remote teams, this would be an embedded team member who is a customer/decision-maker, as opposed to a requirements document.)
  • If code reviews are good, how about we have a continuous code review, with pair programming all the time?
  • If testing is good, how about we unit test before we write the...