You should be able to set doSkipScenariosAfterFailure(true) to make
jbehave stop executing the remaining scenarios. If you set that based
the existence on a property, that should do what you need.
On 12.03.2012 13:47, Maring, Steve X. -ND wrote:
I have stories with many scenarios that need to be run, and those kick
off Selenium tests. For development purposes, it would be really nice to
be able to specify a system property that would tell JBehave to stop
running any new Scenarios if it encounters a failure or error with a
scenario.
I’ve played with implementing org.jbehave.core.failures.FailureStrategy,
but when you set that on the configuration the StoryRunner just holds on
to the failures until finished running the whole story. For me, that can
be a 20 minute wait time from the time I see that a particular Scenario
failed.
Is there a way for me to hook into the step or scenario execution to
catch the exceptions and or errors and stop JBehave from running further?
Thanks,
-Steve Maring
Orlando, FL
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
