[LRUG] TDD (was: Ruby Contracting)

Chris Roos chris at seagul.co.uk
Thu Feb 19 02:06:41 PST 2009


I'm interested in hearing these arguments too.

On Thu, Feb 19, 2009 at 10:03 AM, Stephen Bartholomew <steve at curve21.com> wrote:
> Hey all,
>
> Further to the last few replies, it would be interesting to hear what the
> specific issues are with the TDD process.
>
> Steve
>
> On 19 Feb 2009, at 01:45, Eleanor McHugh <eleanor at games-with-brains.com>
> wrote:
>
>> On 18 Feb 2009, at 21:48, Romek wrote:
>>>
>>> And sadly python is currently more fashionable as there is more
>>> structure there (which really needs the same being applied to ruby
>>> instead of this horrendous test first, code later ethic kicking around
>>> here).
>>
>> I'm reconciled to the fact we won't be winning either of these battles
>> anytime soon ;)
>>
>> The [T|B]DD fad has to run its course. Perhaps when more developers find
>> themselves working with the exacting non-functional requirements we're used
>> to tackling they'll realise the short-comings of relying on automated
>> testing but by then they'll already have moved beyond the "gee whizz we
>> could build a social website" shallows into deeper, darker waters.
>>
>>
>> Ellie
>>
>> Eleanor McHugh
>> Games With Brains
>> http://slides.games-with-brains.net
>> ----
>> raise ArgumentError unless @reality.responds_to? :reason
>>
>>
>> _______________________________________________
>> Chat mailing list
>> Chat at lists.lrug.org
>> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>



More information about the Chat mailing list