Making testability our mission

Room 4

This is a call to action. On our cross functional teams and during our devops transformations 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. It doesn’t have to be this way.

During my talk, I want to introduce a set of principles for testability engineering. A new way to approach our work as testers. 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. I believe it is time to create a new focus on testability, as it affects everything we do, what our teams do and beyond into how value is delivered for customers.

I want you to take away from the talk:

  • Why a focus on what testability can multiply your effectiveness as a tester
  • What the principles of testability engineering are and how to advocate for them
  • How you can make iterative changes to what you do in order to embrace testability

New technology and complexity is rendering many software development techniques and paradigms obsolete at an increasing rate. We already exist in a space where an infinite number of tests of an array of different types can be performed. A new mission is needed, one that leverages the varied talents of all kinds of testers and culminates in a new focus on the exponential benefits that testability brings.

Keynote