A simple, hands-on, introduction to Test Driven Development
Test Driven Development (TDD) is easy to describe:
Write a failing test,2.
Make the test run,3.
Refactor (clean up) the code so the design is cleaner, and4.
Repeat for the next test.You build your working software up small incremental steps, one test at atime. This cuts down hugely on the amount of time required to rework codeto fix defects and time can, instead, be used to refactor the code, keepingthe code-base clean, well designed and malleable, so it is easy and cheap towork with.
Significantly Less rework
significantly easier code
Significantly higher productivity.
Even better, the tests act as a safety net
catching your mistakes quickly sothat they are cheaper and easier to fix.
That's an easy process to describe, but that's not enough: it‟s only when you
truly get it
How do you try TDD, for real, if you’re not a programmer?
How do you persuade your boss to let you do TDD, if he or she can’t
truly get it
Here's how. This site runs through a very simple TDD example
convertingintegers into their roman number equivalent - that you or your boss can doeasily using Microsoft Excel and Visual Basic for Applications (VBA).
teach how to do TDD or how to program, but rather it‟s a hands
on example where you can get a feel for the process and the possibilities.