Did Not Make The Cut #3
Who tests the tests?
Description
This one is rare—but not rare enough.
And if you've seen it before, you already know… this is where things start to unravel.
The moment you realize the tests are passing… but the bug is still very much alive.
That's when your confidence quietly leaves the room.
Because now it's not just the code you don't trust.
It's the tests.
And once that happens… everything becomes a suggestion.
“Who tests the tests?”
Developer Channel
Pete: Ah, the classic “fixed one, broke two.”
Rob: That's what I thought… but the code looks fine.
I think the tests might be wrong.
I think the tests might be wrong.
Pete: Bold claim. Who wrote them?
Rob: Bill.
Pete: The same Bill we just let go?
Rob: Yep.
Pete: Got it. The tests must be wrong.
Question is… is it just those two?
Question is… is it just those two?
Rob: I will open a ticket to look into all his tests.
Lesson Learned
Sometimes fixing a bug doesn't break the tests—
it reveals they were broken the whole time.
But… two unit tests are now failing.