Team Guide to Software Testability

Ash Winter and Rob Meaney

This is a sample of the book's content.Buy on Leanpub

Table of Contents

Team Guide to Software Testability

1. Team Guides for Software
2. Praise for Software Testability
3. Introduction
4. Set a pragmatic direction for improving testability using trade off sliders
5. Create testability targets to improve interactions with dependencies
6. Adopt testability mapping to expose hard-to-test architectures
7. Use historical data to fix design problems that inhibit feedback
8. Adopt ephemeral development environments for fast feedback
9. Use production data to enhance your testing strategy
10. Use team testing reviews to enable sustainable delivery
11. Terminology
12. About the authors
13. Conflux Books

Team Guide to Software Testability/7. Use historical data to fix design problems that inhibit feedback

7. Use historical data to fix design problems that inhibit feedback

(This chapter is not available in this edition of the book.)

Previous

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

Up next

8. Adopt ephemeral development environments for fast feedback

In this chapter

7. Use historical data to fix design problems that inhibit feedback