Yes, the keyword includes the : character and without it the scenario would not get parsed properly, ie it would be considered part of the previous.
You can change the keyword to not include the : if you so wish. Cheers On 3 Mar 2011, at 16:25, "Simon Kent" <[email protected]> wrote: > Found the issue. Had > Scenario : description > > rather than > > Scenario: description > > so the extra space I guess meant that it did not recognise the scenario > change? > > Simon Kent > QA Engineer > Gresham Computing PLC > e: [email protected] > t: +44 1454 222974 > w: http:/www.gresham-computing.com > a: Green Farm Business Park, Latteridge,, Iron Acton, BS37 9TZ > > From: Mauro Talevi > Sent: Thursday, March 03, 2011 10:32 AM > To: [email protected] > Subject: Re: [jbehave-user] AfterScenario skipped after results table > > Hi Simon, > > could you please try upgrading to 3.2 and seeing if the issue persists? > > Also, an example verifying the behaviour of @AfterScenario can be found in: > > https://github.com/jbehave/jbehave-core/blob/master/examples/trader/src/main/java/org/jbehave/examples/trader/stories/after_scenario_outcome.story > > Cheers > > On 03/03/2011 10:58, Simon Kent wrote: >> >> Hi! >> >> I am using JBehave V3.1.2. I have a story with multiple scenarios which uses >> results tables. The AfterScenario code does not appear to run (or at least >> only on the last scenario). Is this a known issue? >> e.g. >> Scenario: scenario1 >> Given xxxx >> When yyyy >> Then we get the data: >> |1|2|3| >> |4|5|6| >> >> !—if we added another step here it does fire the AfterScenario code >> >> Scenario: scenario2 >> .... >
