Christian, Welcome!!
I've seen aliases used as a way to deal with plurals / singular forms of statements. They really are to help with readability. So never anything like 50 aliases - that would be a test-smell. The goal is to have visibility into the regular expressions that are used in the existing @Given/@When/@Then annotations. You can produce just such documentation with StepDoc http://jbehave.org/reference/stable/finding-steps.html I've not tried it myself but that would be a good place to start. Brian ----- Original message ----- From: "Christian Taylor" <[email protected]> To: [email protected] Date: Fri, 16 Dec 2011 15:52:42 +0100 Subject: [jbehave-user] Newbie questions about organising Hi all, Just found and joined this group. Looks like a great resource for help and sharing experiences:) I joined as a result of a specific discussion we are having about scenario steps, as we are about to take the leap into the jBehave world and need to try and understand things a little more in-depth before we commit entirely. We are a small test team of 2 (sometimes 3), but many of the developers also contribute to writing stories. We have a fairly defined divide between authors and implementers - meaning it's so far only the dev teams doing the implementation. That may change in the future, but it's working well for us. Reading through the information available, there seems to be a lot of focus on the implementations, but reading about the alias feature, my toes curl at the thought of a test-suite building up and ending with 50 aliases to 1 implementation. If I am about to embark on writing some new stories and want to make sure that my steps use a syntax which is identical to the existing stories so as to avoid the use of aliases - how is this done? Is it simply a search through the exisiting .story files for the step I have just written? Is there a tool for eclipse or otherwise that aids this? Is it simply a fact of life that aliases are a necessary evil (in my book at least)? Remember I'm referring only to the authoring of the scenarios here, and not the implementation. Thanks Christian --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --- Brian Repko LearnThinkCode, Inc. http://www.learnthinkcode.com email: [email protected] phone: +1 612 229 6779 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
