I'm clearly not explaining it well because that's exactly what I'm advocating!
You DO evolve the language that describes the interactions with the system. But that evolving language is CALLED BY the code inside the methods in the fixture. The method names of the fixture don't change unless the requirements are changed, but their contents may change if the implementation changes.
Essentially, it offers an extra level of indirection, which is valuable because you can change the system interaction language and still have test protection.
Specs -> Instrumentation -> Fixture -> System Interaction Language -> System Under Test
Best regards,
David
On 10 January 2012 22:18, George Dinwiddie <lists@idiacomputing.com> wrote:
Better get it right the first time, then. I'd rather evolve the language
used to describe interactions with the system.
> <mailto:lists@idiacomputing.com>> wrote:
On 1/10/12 5:08 PM, David Peterson wrote:
>
>
> Exactly.
>
> On 10 Jan 2012 22:00, "George Dinwiddie" <lists@idiacomputing.com
>
> __
>> <http://concordian.org>,
> David,
>
> On 1/10/12 4:55 PM, David Peterson wrote:
> >
> >
> > The critical difference is that you almost never need to refactor the
> > instrumentation in a Concordion specification. It's not a
> mini-language
> > that's evolving in the way a Cucumber given/when/then language
> evolves.
> > The instrumentation merely links the contents of the examples in the
> > specification to the fixture. In effect, each specification has
> its own
> > completely independent language that suits its needs exactly.
>
> Are you saying that in the example on concordian.org
>----------------------------------------------------------------------
> <p>
> When <span concordion:set="#firstName">Bob</span> logs in a greeting
> <span concordion:assertEquals="greetingFor(#firstName)">Hello
> Bob!</span>
> should be displayed.
> </p>
>
> you would never rename the method "greetingFor" or change the arguments
> it requires?
>
> - George
--
* George Dinwiddie * http://blog.gdinwiddie.com
Software Development http://www.idiacomputing.com
Consultant and Coach http://www.agilemaryland.org
----------------------------------------------------------------------
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/agile-testing/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/agile-testing/join
(Yahoo! ID required)
<*> To change settings via email:
agile-testing-digest@yahoogroups.com
agile-testing-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
agile-testing-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
__._,_.___
MARKETPLACE
.
__,_._,___
0 comments:
Post a Comment