Mauro Talevi wrote:
now I understand the use case better. It would surely be addressable
by http://jira.codehaus.org/browse/JBEHAVE-126, but in the meantime, the
workaround I've found useful in my projects is to use a naming
convention, together with the fact that scenarios are run in
alphabetical order.
So, if you e.g. prefix your scenarios with an incremental number s<n>,
you can create a s0_client_account_is_setup.scenario that gets executed
as first scenario. Of course, this works if you need to setup the
scenario once, an not before each scenario.
Mmm... sounds too hacky :-)
Alternatively, you could try using the @BeforeScenario annotation in
your Steps instance to execute some setup code. But this has the
disadvantage of not being declarative via a textual scenario.
This I think I can live with for the moment. I'll try it out.
But, as I said above, I'd like kick-start the GivenScenarios approach
again. I hope to get some time soon in the next week or so.
That would be great! Thanks!
/Rickard
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
