From: Eleanor McHugh <eleanor@...>
Date: 2008-08-17T00:27:32+09:00
Subject: Re: BDD and TDD - What are they for?

On 16 Aug 2008, at 15:33, Phlip wrote:
> Here's an example of a test case written in programmer-speak:
>
>  test_strobe_count_down_fields_in_pre_fight_states
>
> Now reverbiage it:
>
>  specify 'the audience sees an animated countdown before the fight' do
>
> Figuring out how to say an internal detail in terms a client can  
> understand is often brain-wrenching. As developers, our brains are  
> prepped with developer terms. The B in BDD stands for "Behavior the  
> client has requested"...

Which of course presupposes there is a clear and direct transformation  
between what the client believes they want, what they actually want,  
what they should actually get (which is not always the same thing) and  
how these can be represented in software given whatever other  
arbitrary requirements apply. I'm too much of a cynic (i.e. have  
worked on too many complex projects with multiple stake-holders) to be  
convinced of this fact, but I definitely wouldn't discourage anyone  
else from giving it a go as different tools work for different people :)


Ellie

Eleanor McHugh
Games With Brains
http://slides.games-with-brains.net
----
raise ArgumentError unless @reality.responds_to? :reason