Team Guide to Software Testability
This book is 11% complete
Last updated on 2018-12-05
About the Book
Team Guide to Software Testability is the third guidebook in the new collection from Skelton Thatcher Publications.
A practical guide to how testability can help bring teams together to observe, understand and control the systems they build. Enabling them to better meet customer needs, achieve a transparent level of quality and predictability of delivery.
The ‘Team Guide’ collection is designed to help teams building and running software systems to be as effective as possible.
Guides are curated by experienced practitioners and emphasise the need for collaboration and learning, with the team at the centre.
Manuel Pais is an independent DevOps and Delivery Consultant, focused on teams and flow.
With a diverse experience including development, build management, testing and QA, Manuel has helped large organizations in finance, legal, and manufacturing adopt test automation and continuous delivery, as well as understand DevOps from both technical and human perspectives.
Manuel is co-author of the Team Guide to Software Releasability book and lead editor for the remaining books in the Team Guide series.
- The Team Guide series
- Why is testability important
- What does hard to test feel like
- What does testable feel like
- What leads to testability being neglected
- What is covered in this book
- How to use this book
- Feedback and suggestions
- 1. Use a testability inception deck to visualise current team and system state and create an environment for improvement
2. Adopt testability mapping to expose common smells of hard to test architectures
- 2.1 Gathering data on poor architectural testability to detect systemic problems
- 2.2 Low testability architectures contribute to slow feedback and deficient decision making
- 2.3 Identify the symptoms of poor architectural testability
- 2.4 Exercise: Measure the impact of testing smells on your architectural testability
- 2.5 Understand how testable architecture can impact your team’s testing efforts
- 2.6 Summary
- 3. Use risk and incident data to remedy architectural design problems which inhibit feedback from testing
- 4. Adopt ephemeral development environments to diversify testing techniques early and create shorter feedback loops
- 5. Utilise events and metrics to model risks in production for continuous improvement of your test strategy
- 6. Adopt incident postmortems to maintain a testability focus as part of your team’s continuous improvement strategy
- About the authors
This book is published on Leanpub by Skelton Thatcher Publications
Developing and running modern software systems requires teams of motivated and well-trained people; however, most IT books are written for the individual technologist. The Team Guide series from Skelton Thatcher Publications takes a team-first approach to software systems with the aim of empowering whole teams to build and operate software systems more effectively.
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms...