how are you supposed to know what the code is supposed to do? That's the beauty of TDD. It forces you to sit and work out, "What is this code supposed to do f

how are you supposed to know what the code is supposed to do? That's the beauty of TDD. It forces you to sit and work out, "What is this code supposed to do from the client perspective?" It battles the all-too-prevalent developer inclination to just start running with implementation without even taking the time to understand what problem is being solved.