[jbehave-dev] [jira] (JBEHAVE-1053) Allow entire story to be restarted

[Brent Barker (JIRA)]

Title: Message Title

Brent Barker commented on an issue   Re: Allow entire story to be restarted Great, thank you very much! I tried the code, and if an exception is thrown from a before/after annotated method, it does not restart the story. Exceptions that happen in that area only gets logged, and does not get saved off anywhere. The scenario would be like this: If a story fails, call the annotated method: @AfterScenario(uponType = ScenarioType.NORMAL, uponOutcome = Outcome.FAILURE) public void afterNormalScenario(UUIDExceptionWrapper uuidWrappedFailure) Inside of that method, would be logic to restart the story if it fails the first time. Other then that don't restart. I'll see if I can add that logic to the restarting.story, but I may have to edit a lifecycle method somewhere to do this. Add Comment   JBehave / JBEHAVE-1053 Allow entire story to be restarted For selenium tests that keep the same browser / context throughout the story, there are countless things that can go wrong such as network latency, slow application, etc. Since a false positive can cause people to quickly lose trust in the tests, others advised that the story should restart "x" amount of times before failing the test. There is a way to... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email