Mauro Talevi wrote:
Right, so what I want to do then is to package the above into
something which sets up my "assumed state", so I don't have to repeat
it over and over again. Almost like, "Given a logged in account",
where this entails creating the account, setting the settings, logging
in and accessing the inbox. *Then* I want to create scenarios using
that inbox. How do I do this kind of scenario composition best?
Not really sure what you mean here.
A given setup can be implemented to do whatever you need to set up the
assumed state, including invoking methods on other services.
Can you give me more details please?
Ok, I want this to be a "setup":
Given a client
When I add an account
Then an account is added
Given an account
When I change settings to username=rickardoberg, password=rickardoberg,
server=http://localhost/
Then settings are updated
Given an account
When I register
The user is registered
Given an account
When I connect
Then the account is connected
---
The above is what in my case is required to start doing anything at all
in the UI. I could repeat them in every single scenario I need to do,
but that seems like a waste. So, I want to encapsulate this base
scenario in some way so that I can then easily build other scenarios on
top of it. What is the best way to do this?
/Rickard
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
