Re^2: Does anybody write tests first?

I was speaking more about the design side, using it more, to borrow your words, as a blunt tool to design the project. My idea (which as I guessed is not even close to a new concept) was just to combine the time spent spec'ing out the project with the time that would be spent later on writing tests.

What do you do as your first step in the design?

Comment on Re^2: Does anybody write tests first?

Replies are listed 'Best First'.
Re^3: Does anybody write tests first? by educated_foo (Vicar) on Feb 22, 2008 at 17:00 UTC
I think about the problem and solution, trying to come up with its governing laws. Sometimes I write math and pseudocode in a notebook.	[reply]
Re^4: Does anybody write tests first? by amarquis (Curate) on Feb 22, 2008 at 17:56 UTC
Sounds like how I approach a physics problem (physics is a domain where I've much more knowledge than programming): just think about the problem and constraints, and then "just do it." I think that you are right, that tests as a design tool are somewhat of a crutch for the inexperienced. But, as far as crutches go, they seem to be a pretty good one. The automated tests you create during design follow through and help you during development, and it gets you thinking about the module user's experience.	[reply]


We don't bite newbies here... much
	PerlMonks