John wrote: > I quite like the idea of writing the tests first. The problem with this is that you don't know what to test for until you've written the code.
Maybe some much more organised people than me can specify exactly what they want upfront, then write the tests to reflect the specification, then write the code to pass the tests. But an acknowledged problem with software development is that you don't really know what you want when you start out (you just think you do), it's difficult to write a watertight spec, and ideas evolve as the project progresses and in response to user feedback. My personal solution is to write the tests and the code in parallel, a few lines at a time. The way I exercise the code is by running the tests. David
