CHAPTER 4
What Are We Doing with All These Tests?
Now that we’ve seen the basics of TDD in action, it’s time to pause and talk about why
we’re doing it.
I’m imagining several of you, dear readers, have been holding back some seething frus‐
tration—perhaps some of you have done a bit of unit testing before, and perhaps some
of you are just in a hurry. You’ve been biting back questions like:
• Aren’t all these tests a bit excessive?
• Surely some of them are redundant? There’s duplication between the functional
tests and the unit tests.
• I mean, what are you doing importing
django.core.urlresolvers
in your unit
tests? Isn’t that testing Django, ie, testing third-party code? I thought that was a no-
no?
• Those unit tests seemed way too trivial—testing one line of declaration, and a one-
line function that returns a constant! Isn’t that just a waste of time? Shouldn’t we
save our tests for more complex things?
• What about all those tiny changes during the unit-test/code cycle? Surely we could
have just skipped to the end? I mean,
home_page = None
!? Really?
• You’re not telling me you
actually
code like this in real life?
Ah, young grasshopper. I too was once full of questions like these. But only because
they’re perfectly good questions. In fact, I still ask myself questions like these, all the
time. Does all this stuff really have value? Is this a bit of a cargo cult?
35