Team Guide to Software Testability
Team Guide to Software Testability
Minimum price
Suggested price
Team Guide to Software Testability

This book is 30% complete

Last updated on 2019-03-08

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.

About the Authors

Ash Winter
Ash Winter

Ash Winter is a continuously learning tester with a penchant for getting involved in all aspects of developing people, products and organisations. His career spans consultancy, veteran of various engagements encompassing testing, performance engineering and automation, being a team member delivering mobile apps and web services or a leader of teams and change. He also coaches, blogs and speaks at tech meetups, across many disciplines. Quite busy but always has time for a question, usually answered with another question.

Rob Meaney
Rob Meaney

I'm Rob Meaney a tester that loves tough testing and software delivery problems. I work with teams to help improve the quality of their software products and processes while also having fun. Although I enjoy learning about software delivery in general I'm particularly interested in Quality Engineering, Test Coaching, Testability, and Testing in Production.

Currently, I'm working as Head of Testing & Test Coach for Poppulo in Cork, Ireland. I'm an active member of the online testing community and co-founder of Ministry of Test Cork.

Previously I've has held positions as Test Manager, Automation Architect and Test Engineer with companies of varying sizes, from large multinationals like Intel, Ericsson & EMC to early-stage startups like Trustev. I've worked in diverse areas from highly regulated industries like safety automation & fraud detection to dynamic, exciting industries like gaming.

About the Contributors

Manuel Pais
Manuel Pais

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.

Table of Contents

  • The Team Guide series
  • Foreword
  • Introduction
    • 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 and create shorter feedback loops
    • 4.1 Common challenges with creating, using and maintaining test environments
    • 4.2 Leveraging your development environment for fast feedback
    • 4.3 Enhancing your development environment for balanced testing
    • 4.4 Summary
  • 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
  • Terminology
  • About the authors
  • Notes

About the Publisher

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...

Write and Publish on Leanpub

Authors, publishers and universities use Leanpub to publish amazing in-progress and completed books and courses, just like this one. You can use Leanpub to write, publish and sell your book or course as well! Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks. Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. It really is that easy.

Learn more about writing on Leanpub