The "finally" step is not currently an option.
What you can do is write to a file the info required during the exec of
steps (e.g. the username) and then use that to implement the
@AfterScenario step.
On 06/01/2012 13:23, Alex Lehmann wrote:
Thanks, I have now considered if this solves my problem, I think I
need a step that has access to the parameters of the scenario, either
with a $-parameter or to the values of the examples table.
What I would like to do is similar to a catch or finally block, i.e.
run a step regardless if a previous step in the scenario fails.
E.g. if I want to check if a record in a db table can be created,
updated and delete, I need to delete it even if the create or update
step failed to avoid filling up the database (assuming that the
database is not a mockup).
something like
given i create an entry name <username>
when i read the entry <username>
then the entry <username> is present
finally delete the entry <username>
I'm not sure if this is a good idea, but I think I need this to create
repeatable tests for my project.
On 29.12.2011 18:08, Brian Repko wrote:
Alexander,
You can implement @BeforeScenario and @AfterScenario methods.
There are various parts of the lifecycle that you can hook into.
You can find those in the documentation
http://jbehave.org/reference/stable/annotations.html
Brian
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
