Typically you would define an API to access these variables. This is
something that you cannot really generalise.
If on the other hand you know these variable at execution time, you could pass
them as system properties in the jbehave maven goal or ant task.
On 31 Oct 2013, at 11:12, Hans
I see. So there is no use looking for a existing JBehave feature for this.
I meant dynamic variables which are set and used at runtime. There are
cases where one has to automate tests on non-deterministic test data (I
mean the data of the application under test).
A life cycle of these variables
We also have several scenarios where the input for the scenarios are determined
at runtime.
I think Paul offered a good solution, create a variable in the pageObject and
set it (by the When step) then you can get it (on the Then step) for
verification (I think we'll give this approach a
