I'm a little confused by what you are asking... as I don't understand why jbehave would be worried about this...
If I understand you correctly, why wouldn't you just write a page object method that returns the account balance then write steps to do the actions you want and have a Then step that assertTrue (expectedParameter.equals (accounts.getBalance ()); Long story short I believe you should implement yourself... Hopefully this info helps, P Sent from my MetroPCS 4G Wireless Phone -------- Original message -------- From: Hans Schwäbli <[email protected]> Date: 10/31/2013 6:12 AM (GMT-05:00) To: [email protected] Subject: [jbehave-user] Support for dynamic variables? 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?
