1 - Same as Brian, just beware of shared data between scenarios 2 - I would use maven to do that, within the same build phase the plugins order is the execution order Example : <plugin>dbunit</plugin> <plugin>jetty</plugin> <plugin>jbehave</plugin> will run dbunit, then jetty, then jbehave
3 - Encapsulate your test data in an object and clean it in @BeforeScenario, just as you would use @Before in junit, it will ensure scenarios independance. Hope it helps. -- Cordialement/Regards, Louis GUEYE linkedin <http://fr.linkedin.com/in/louisgueye> | blog<http://deepintojee.wordpress.com/> | twitter <http://twitter.com/#%21/lgueye> 2012/4/4 rakesh mailgroups <[email protected]> > Hi, > > I would like to ask: > > 1. Is there a way to avoid having to write a JUnit class per story file? > 2. If I need to do some tasks before running the tests once (deploy war in > my case) how would I do that? > 3. My When section gets some data and my Then section asserts on it. Is it > ok to create an instance field in the Steps class and assign in one step > and use it in another? Seems a bit hacky. > > Thanks > > Rakesh >
