Take the 2-minute tour ×  I know that one of the defining
principles of Test driven development is that you write your
Unit tests first and then write code to pass those unit tests,
but is it necessary to do it this way?  I've found that I often
don't know what I am testing until I've written it, mainly
because the past couple of projects I've worked on have more
evolved from a proof of concept rather than been designed.  I've
tried to write my unit tests before and it can be useful, but it
doesn't seem natural to me.  share|improve this question Please,
make this community wiki, as it's more than poll than real
question. –  Sunny Milenov Oct 29 '08 at 14:51 This ought to be
a real question, rather than yet another poll. I'd prefer Omar
reworded the question slightly to make it a proper question,
rather than a poll-type question. –  David Arno Oct 29 '08 at
14:53 I'm happy to reword I'm not sure what to re-word it to
though. –  Omar Kooheji Oct 29 '08 at 14:56 How about something
along the lines of "When is t