Ideas for testing improvement are everywhere – write some tooling, test in production, shift testing left, “sprinkle some AI on it”, and so on.
But how will we know if they work?
Over the years, we’ve come up with a few ways to measure test improvement. These are not bug counts, but instead measurements of system performance. Before trying any change, we can ask “what should this change do to these measures?” If the answer is “it will make them worse”, we can pause and think. Likewise, we can check before and after and see if the measures improve. Of course, the real outcome we want is “less complaining customers”, “more free time to add new features”, “less arguing in circles” and so on.
Specifically, we are talking about cycle time, lead time, and touch time, along with coverage measures.
Want to learn how to do them in twenty minutes? Our Managing Director, Matt Heusser, will tell you how at the SDTimes Improve testing series on March 20 at 11AM Eastern. The event is at no cost, the session is about a half hour.