(Joel, please preserve attribution lines on your quoted material so we
can see who wrote it.)
Joel Hedlund <[EMAIL PROTECTED]> writes:
> My presumption has been that in order to do proper test-driven
> development I would have to make enormous test suites covering all
> bases for my small hacks b
Diez B. Roggisch wrote:
> Sounds good to me. IMHO there are two ways one gathers tests:
>
> - concrete bugs appear, and one writes a test that reproduces the bug &
> eventually after the fix runs smoothly
>
> - new features are planned/implemented, and the tests accompany them right
> from the
> On Behalf Of Joel Hedlund
> My presumption has been that in order to do proper
> test-driven development I would have to make enormous test
> suites covering all bases for my small hacks before I could
> getting down and dirty with coding (as for example in
> http://www.diveintopython.org/uni
Joel Hedlund wrote:
>> test-driven development merely means that you take that test case and
>> *keep it* in your unit test. Then, once you're assured that you will
>> find the bug again any time it reappears, go ahead and fix it.
>
> My presumption has been that in order to do proper test-driven
> test-driven development merely means that you take that test case and
> *keep it* in your unit test. Then, once you're assured that you will
> find the bug again any time it reappears, go ahead and fix it.
My presumption has been that in order to do proper test-driven development I
would have t
Joel Hedlund <[EMAIL PROTECTED]> writes:
> Do you also do [test-driven development] for all the little stuff,
> the small hacks you just whip together to get a particular task
> done? My impression is that doing proper unittests adds a lot of
> time to development, and I'm thinking that this may b
