:) I did see the issue, of course, but I can't get your code to compile, so I wasn't able to put the fix in myself. I was sort of hoping there was something I could put in my @AfterScenario or something. I will try to get a build to work again, and will watch for 3.5.
Thanks for the quick response. Vicki On Mon, Jun 27, 2011 at 5:32 PM, Mauro Talevi <[email protected]>wrote: > ** > https://jira.codehaus.org/browse/JBEHAVE-547 > > > On 27/06/2011 22:34, Vicki Sainz wrote: > > Hi all. > > I am experiencing this in our tests, now that I have upgraded to JBehave > 3.4. I'm assuming runParametrisedScenariosByExamples is when a scenario > uses an Examples: table for parameters? > > Is there a workaround, until this is fixed? > > What release of JBehave will this make it into? > > Thanks, > Vicki > > > > On Sat, Jun 25, 2011 at 2:18 AM, Mauro Talevi > <[email protected]>wrote: > >> Hi, >> >> can you please raise issue at http://jira.codehaus.org/browse/JBEHAVE? >> >> Cheers >> >> On 24/06/2011 21:25, Plamen Gurov wrote: >> > Currently, the method StoryRunner.runParametrisedScenariosByExamples >> does not >> > check the configuration and whenever a step fails all subsequent >> examples are >> > reported as not performed. >> > >> > A simple fix would be to do this before calling the runScenarioSteps >> method: >> > >> > if(context.configuration().storyControls().resetStateBeforeScenario()) { >> > context.resetState(); >> > } >> > >> > Thanks >> > >> > >> > --------------------------------------------------------------------- >> > 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 >> >> >> > > > -- > -vicki 512-731-6618 > > > -- -vicki 512-731-6618
