I've done test-driven-design/development but never written a whole
bunch of tests before writing any of the implementation code.
In the tests-as-spec area, how about writing a number of "user
acceptance tests" up front, as opposed to Unit Tests. The acceptance
tests could be in .t files if you like but would exercise the code
from a users point of view, and would be free to do things like talk
to a real database, etc.
On Jun 19, 2007, at 8:52 AM, Mike Malony wrote:
So I'm working my project, and I've got one other more junior coder
with
me.
Has anyone tried writing test files as part of their spec's?
An overview document would also be needed, and some time walking
through the
expected testing. But it sure would be setting clear expectations.
Comments?
Mike
-------------------------------------------------------
Matisse Enzer <[EMAIL PROTECTED]>
http://www.matisse.net/ - http://www.eigenstate.net/
