One of the exercises I love to do in my TDD classes is to build a lightsaber in TDD. (Yes, of course that’s how they’re made). In the exercise, I go through listing all kinds of features and use cases, and the first test we usually write is for turning Read more…
in the last post we talked about the failing builds trend as an indicator of success of implementation. The final metric we’ll look at, that can indicate how our process will go, is also related to broken builds. It is the “time until broken builds are fixed” or TUBBF. Ok, Read more…
Part I was HUGE! Now, let’s look at broken builds. We want to see a decrease in their number over time. This may sound a bit strange. Our CI is supposed to tell us if the build breaks, that’s its job. Isn’t having more of them a good thing? Unsurprisingly, Read more…
Now that we’ve talked about what we want to achieve, we better spread out some sensors. After all, we’re about to embark on a long and winding road. We want to know if we’re still going the right way, and if not, make a turn. Leading indicators raise the red Read more…
This conversation comes up in every training I do about testing. I know exactly when it will happen. I know what I’m going to say, what they will say, and I know no one comes out completely convinced. Then violence ensues. We want to test some code. However, this code had Read more…
