There is one main file:
This repository holds a set of testability engineering principles that are designed to guide us during the transformation of the role of testability within teams, especially focusing on how testers of all backgrounds, skills and intent can contribute.
This is a call to action. On our cross functional teams we talk about how testing is for the whole team. Quality is everyone's responsibility. How much are we really doing to make this happen? Often we are working on systems that are hard to test for many reasons, but if we simply do more testing, write more automation we are neglecting what should be our main mission, advocating for increasing levels of testability, to truly get everyone involved in testing. We all have stories about how something is difficult to test, often never being tested or certainly left with the tester to figure it out.
We want to introduce a set of principles for testability engineering. These principles will tackle how we make our systems more observable, controllable, how we share knowledge across teams and improve the testability of our dependencies. We believe it is time to create a new focus on testability, as it affects everything we do, what our teams do and how value is delivered for customers.
For more information on how to get started with testability engineering:
- Team Guide to Software Testability
- Questions to assess the testability of software systems
- 30 Days of Testability
We hope that these principles about testability engineering encourage you to change and improve both your own system, the integration with your dependencies and your relationship with the teams around you.
Testability Engineering by Ash Winter and Rob Meaney is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
