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 Schwäbli <[email protected]> wrote: > For some stories and scenarios I need dynamic variables which are determined > at runtime. > > Example: I want to store the balance of an account, do some transactions and > then expect that the balance is increased by 1000 for instance. If your test > data are not deterministic you need such approaches. > > Is there a JBehave feature for this, storing such dynamic variables at > runtime and accessing them at runtime across scenarios and stories? > > Or do I have to implement that myself in my steps? --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
