Team Guide to Software Testability

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
    • 3.1 Why is testability important?
    • 3.2 What does hard-to-test feel like?
    • 3.3 What does testable feel like?
    • 3.4 What leads to testability being neglected?
    • 3.5 What is covered in this book?
    • 3.6 How to use this book
    • 3.7 Why we wrote this book
    • 3.8 Feedback and suggestions
  • 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
    • 6.1 Poor architectural testability causes slow feedback and flawed decisions
    • 6.2 Identify the symptoms of poor architectural testability
    • 6.3 Exercise: Use testing smells to diagnose poor architectural testability
    • 6.4 Exercise: adopt testability mapping to measure testing feedback and waste
    • 6.5 Summary
  • 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/5. Create testability targets to improve interactions with dependencies

5. Create testability targets to improve interactions with dependencies

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

Previous

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

Up next

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

In this chapter

  • 5. Create testability targets to improve interactions with dependencies