Re: [jbehave-user] graceful stop after first failed story ?
Hi Steve, you can set EmbedderControls.doIgnoreFailureInStories(false) Or you can set the property ignoreFailureInStories=false via Maven or Ant in command-line. Cheers On 21/03/2012 19:18, Maring, Steve X. -ND wrote: I see how from within a StoryRunner I can override the run(...) and set a FailureStrategy on the configuration. However, I'm trying to figure out if there is something I can instantiate my FailureStrategy with that will allow me to stop running any additional stories when handleFailure(...) is called. Currently, I'm just logging the throwable and doing a System.exit(-1), but that isn't the most graceful thing in the world. I like how configuration.storyControls().doSkipScenariosAfterFailure(true) will stop running any more Scenarios in a Story when a Scenario fails. It would be cool if I could stop running any more Stories upon encountering a failed Story, short of a System.exit. Any ideas? Thanks, Steve Maring
RE: [jbehave-user] graceful stop after first failed story ?
I'm actually doing ... configuredEmbedder().embedderControls() .doGenerateViewAfterStories(true) .doIgnoreFailureInStories(false) .doIgnoreFailureInView(true); ... but it seems to keep running stories after encountering failed ones. I'm using JBehave 3.1.1. Is it possible it wasn't implemented properly back then? From: Mauro Talevi [mailto:mauro.tal...@aquilonia.org] Sent: Thursday, March 22, 2012 6:23 AM To: user@jbehave.codehaus.org Subject: Re: [jbehave-user] graceful stop after first failed story ? Hi Steve, you can set EmbedderControls.doIgnoreFailureInStories(false) Or you can set the property ignoreFailureInStories=false via Maven or Ant in command-line. Cheers On 21/03/2012 19:18, Maring, Steve X. -ND wrote: I see how from within a StoryRunner I can override the run(...) and set a FailureStrategy on the configuration. However, I'm trying to figure out if there is something I can instantiate my FailureStrategy with that will allow me to stop running any additional stories when handleFailure(...) is called. Currently, I'm just logging the throwable and doing a System.exit(-1), but that isn't the most graceful thing in the world. I like how configuration.storyControls().doSkipScenariosAfterFailure(true) will stop running any more Scenarios in a Story when a Scenario fails. It would be cool if I could stop running any more Stories upon encountering a failed Story, short of a System.exit. Any ideas? Thanks, Steve Maring
Re: [jbehave-user] graceful stop after first failed story ?
It's possible that there were issues on 3.1.1. But why are you not on the latest stable version? Also bear in mind that the Maven or Ant config (command-line) will override anything configured via Java. On 22/03/2012 12:38, Maring, Steve X. -ND wrote: I'm actually doing ... configuredEmbedder().embedderControls() .doGenerateViewAfterStories(*true*) .doIgnoreFailureInStories(*false*) .doIgnoreFailureInView(*true*); ... but it seems to keep running stories after encountering failed ones. I'm using JBehave 3.1.1. Is it possible it wasn't implemented properly back then? *From:*Mauro Talevi [mailto:mauro.tal...@aquilonia.org] *Sent:* Thursday, March 22, 2012 6:23 AM *To:* user@jbehave.codehaus.org *Subject:* Re: [jbehave-user] graceful stop after first failed story ? Hi Steve, you can set EmbedderControls.doIgnoreFailureInStories(false) Or you can set the property ignoreFailureInStories=false via Maven or Ant in command-line. Cheers On 21/03/2012 19:18, Maring, Steve X. -ND wrote: I see how from within a StoryRunner I can override the run(...) and set a FailureStrategy on the configuration. However, I'm trying to figure out if there is something I can instantiate my FailureStrategy with that will allow me to stop running any additional stories when handleFailure(...) is called. Currently, I'm just logging the throwable and doing a System.exit(-1), but that isn't the most graceful thing in the world. I like how configuration.storyControls().doSkipScenariosAfterFailure(true) will stop running any more Scenarios in a Story when a Scenario fails. It would be cool if I could stop running any more Stories upon encountering a failed Story, short of a System.exit. Any ideas? Thanks, Steve Maring
