In large scale, high transaction systems testability really is critical, as compared to the vastness and variability of the world, testing done within organisations, before deployment, is limited by comparison. We need ways to see and learn from the systems we test where it matters, in Production.
Being able to observe, control and understand is central to testing effectively, and there are loads of resources and experience reports out there to help. I was/am inspired by James Bach, Seth Eliot, Matt Skelton, Sally Goble, Martin Fowler and a little bit of PerfBytes/Logchat, so lets see if it works for you!
Heuristics of Software Testability by James Bach
In particular, the intrinsic testability of a system. I firmly believe that a system with high testability has high supportability in this regard. If you could build a system that gave those with operational responsibility with the ability to observe, control and understand what was happening, they would be stoked right?
Sally Goble then talks about shifting testing away from current models and leveraging production:
Testing Logging and Monitoring
Data Driven Quality
Signal vs Pass/Fail
Ask for Testability – Interesting Idea on Scriptable API’s to drive the product
A Map for Testability – Visualising testability in early product conversations
Putting Your Testability Socks On – Analysis of the SOCKS testability mnemonic
Architecture workshop from TestBash 2016