Team Guide to Software Testability

Team Guides for Software

Conflux Books

Acknowledgements

Praise for Software Testability

Exercises

Introduction

1. Why is testability important?
2. What does hard-to-test feel like?
3. What does testable feel like?
4. What leads to testability being neglected?
5. What is covered in this book?
6. How to use this book
7. Why we wrote this book
8. Feedback and suggestions

1.Set a pragmatic direction for improving testability using trade-off sliders

1. Key points
2. 1.1Overcome common challenges to setting a team testability focus
3. 1.2Exercise: do the Team Test for Testability for a quick testability health check
4. 1.3Exercise: use Trade-Off Sliders to guide your testability focus
5. 1.4Summary

2.Create testability targets to improve interactions with dependencies

1. Key points
2. 2.1Recognize needs and contributions from different roles to create an effective testability mindset
3. 2.2Exercise: employ Testability Dependency Targets to improve interactions with dependent teams and systems
4. 2.3Summary

3.Adopt testability mapping to expose hard-to-test architectures

1. Key points
2. 3.1Poor architectural testability causes slow feedback and flawed decisions
3. 3.2Identify the symptoms of poor architectural testability
4. 3.3Exercise: Use testing smells to diagnose poor architectural testability
5. 3.4Exercise: adopt testability mapping to measure testing feedback and waste
6. 3.5Summary

4.Apply the CODS model to increase architectural testability for faster feedback

1. Key points
2. 4.1Explicitly design your architecture for testability
3. 4.2Principles of implementing high testability architectures
4. 4.3Exercise: Use ‘CODS’ to increase architectural testability
5. 4.4Moving from hard-to-test to high architectural testability
6. 4.5Summary

5.Adopt ephemeral development environments for fast feedback

1. Key points
2. 5.1Common challenges with static test environments
3. 5.2Use your development environment for fast feedback
4. 5.3Exercise: Use the Agile Test Quadrants to extend testing in your development environment
5. 5.4Summary

6.Use production data to enhance your testing strategy

1. Key points
2. 6.1Static test strategies cause problems in dynamic production environments
3. 6.2Exercise: employ data from production to keep your test strategy relevant
4. 6.3Use deploy and release patterns for feedback on high risk changes
5. 6.4Summary

7.Use team testing reviews to enable sustainable delivery

1. Key points
2. 7.1Testing debt affects wellbeing and sustainable delivery
3. 7.2Adopt a whole-team approach to minimizing testing debt
4. 7.3Exercise: use the 10 P’s of Testability to track team testing culture
5. 7.4Exercise: adopt incident reviews to target testability improvement actions
6. 7.5Create a board to visualize & prioritize testing debt
7. 7.6Summary

Terminology

References

1. Chapter 1 - Testability Priorities
2. Chapter 2 - Testability and Dependencies
3. Chapter 3 - Testability Mapping
4. Chapter 4 - Architectural Testability
5. Chapter 5 - Ephemeral Development Environments
6. Chapter 6 - Use Production to Enhance Test Strategy
7. Chapter 7 - Team Testing Reviews for Sustainable Testability

Appendix - Notes on 10 P’s of Testability

1. 1 - People
2. 2 - Philosophy
3. 3 - Product
4. 4 - Process
5. 5 - Problem
6. 6 - Project
7. 7 - Pipeline
8. 8 - Productivity
9. 9 - Production Issues
10. 10 - Proactivity

About the authors

Index