Abstract
Test-Driven Development treats unit testing as an integral part of the design and implementation process. Often summarized as “test first, code after”, TDD is actually a recognition that in writing tests, we are
With our new knowledge of unit-testing frameworks, ideally, we have made it easier to write self-checking unit tests than to write the actual code to be tested.
The test-first philosophy is easiest to understand in a maintenance/debugging context.
Before attempting to debug, write a test that reproduces the failure.
How else will you know when you’ve fixed it?
From a practical point of view, debugging generally involves running the buggy input, over and over, while you add debugging output or step through with a debugger.
Every few years, software designers rediscover the principle of writing tests before implementing code.
Agile and TDD (Test-Driven Development) are just the latest in this long chain.
Writing tests while “fresh” yields better tests than when they are done as an afterthought.
Thinking about boundary and special values tests helps clarify the software design
Encourages designing for testability
In writing a test, you are actually writing sample code of how the unit’s interface can be used.
Valuable as documentation
It’s very common when writing tests to discover that the interface is incorrect or inadequate.
The very act of trying to write black-box tests becomes itself an exercise in validation of the interface design!
Test-Driven Development (TDD) is the practice of repeatedly:
Write an automated test case for a new desired behavior.
This case must, initially, fail.
Write just enough new code to pass the test.
Refactor the code to make it acceptable quality.
This ties in very nicely with some of our previous discussion of incremental development. In particular, compare to the way we break stories into tasks.
Here you can see a plot of test cases on the vertical axis versus time (actually, commits to the version control system) on the horizontal axis during a project on which I practiced TDD.
Tests passed are shown in blue and failed tests are shown in red.
Notice the repeated pattern:
There are multiple sudden rises in the number of tests failed.
Each such rise is followed by an eventual decrease in the number of failed tests while the total number of tests stays constant (so the blue area grows).
That’s because, after developing the new tests, we started working on implementing the new funcitonality, eventually passing most of those new tests.
There remains, through most of the project, a base set of red tests that we never quite pass.
My stereotypical division of a story into tasks is typically
Compare this to the steps of TDD, above, and you can see that they are compatible.
Here are some short videos illustrating my application of task 1 and task 2 of a story for the Embeddable Spreadsheet project.