[jbehave-user] Fwd: Transitive Scenarios

2013-09-12 Thread Hans Schwäbli
Great, thank you for that answer. I was looking for something like Given Scenario, but this is not the JBehave concept as it seems. The scenarios seem not to be intended to be independent from each other. They seem to be run always in sequential order. So I can re-model this to achieve my goal

[jbehave-user] Re: Transitive Scenarios

2013-09-12 Thread Hans Schwäbli
Unfortunately there seems to be a bug concerning GivenStories in 4.0-beta-3. It did not work with that version. But it works with JBehave 3.8.0. 2013/9/12 Hans Schwäbli bugs.need.love@gmail.com Great, thank you for that answer. I was looking for something like Given Scenario, but this is

[jbehave-user] Re: Transitive Scenarios

2013-09-12 Thread Hans Schwäbli
I discovered that this kind of usage does not work in JBehave 3.8: GivenStories: stories/login_story.story, stories/logout_story.story, stories/login_story.story Scenario: Login after logout to verify if re-login works Only if I add a Given/When/Then, the scenario Login after logout is

Re: [jbehave-user] Re: Transitive Scenarios

2013-09-12 Thread Mauro Talevi
You're right, currently if there are no steps in a scenario the given stories are not executed as they are seen as preconditions to some steps in the scenario. We could make this behaviour configurable though.Currently there no workarounds other than adding at least one step. Note that

[jbehave-user] Execute all scenarios despite of failures

2013-09-12 Thread Bruno Vercelino da Hora
Hi, I'm using JBehave with JUnit. I was able to configure and use it well. But there is something that is bottering me. When a scenario fails all the other scenarios aren't executed, they just show like PENDING. Is there a way that despite a scenario fails the others will be executed? Thanks

RE: [jbehave-user] Execute all scenarios despite of failures

2013-09-12 Thread Jorge Pombar
Hi Bruno, You can control this behavior via configuration. I'm assuming you are talking about scenarios on the same story file The class that controls this on JBehave is org.jbehave.core.embedder.StoryControls. I do find it weird that you see this behavior because I see that the default on