I thought I might as well go ahead and post an example of what worked for me... my conditions were odd JUnit test naming conventions that I'd have to challenge to get my scenarios ran from CI. Thankfully, now I can have one JUnit testcase that has a separate test method for each scenario text file. My finished version is a little cleaner, but here's the basics that got me started:
http://gist.github.com/294199 Thanks, James On Wed, Feb 3, 2010 at 11:32 AM, Mauro Talevi <[email protected]> wrote: > No worries, glad you found the answer you were looking for! > > On 03/02/2010 16:20, James Carr wrote: >> I suppose this was really a case of "Read The Fine Manual" before >> asking questions... >> http://jbehave.org/reference/latest/configuring-scenarios.html gave me >> the info I needed. :) >> >> Thanks, >> James >> >> On Wed, Feb 3, 2010 at 8:14 AM, James Carr <[email protected]> wrote: >>> Hi All, >>> >>> Is there a way to change the way that JBehave looks for a scenario >>> text file when running a Scenario test from junit? I'm currently on a >>> client site that has an enforced naming policy and it causes my >>> scenario text files to have weird names ( like foo_scenario__a_t). >>> >>> Thanks, >>> James >>> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
