
all of the requirements up front because one is going to write the tests for those
requirements.
The problem is that there will not be as much time to modify those tests
later as the requirements change. It would be far better to spend the time
building the prototype first without the tests, get it into the hands of the
users, and then write the tests. That way you write fewer unnecessary tests
and spend more time getting in tune with what the customer really
wants. Then, to raise the overall quality of the application, you write
only those tests that give you the biggest bang for your efforts. This is not
unlike using a code profiler to determine