|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [jbehave-dev] [jira] (JBEHAVE-921) Share immut... Barrie McGuire (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-921) Share ... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-921) Share ... Mauro Talevi (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-921) Share ... Sebastian Sickelmann (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-921) Share ... Sebastian Sickelmann (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-921) Share ... Sebastian Sickelmann (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-921) Share ... Barrie McGuire (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-921) Share ... Sebastian Sickelmann (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-921) Share ... Sebastian Sickelmann (JIRA)
- [jbehave-dev] [jira] (JBEHAVE-921) Share ... Mauro Talevi (JIRA)
Hi Barrie,
Thanks for your comment. I think i will start discussion on comp.java.jbehave.devel with my idea of story and scenario scoped injections.
Just one last question, because i don't see the point of:
"The idea here is that each step should only ever see the state of the world when the previous step has finished - with no possibility of anything else ever affecting it."
As i understand the jbehave-core code the execution of a story is always in a single thread, only multiple stories are eventually executed in parallel. I don't see where my prototyp breaks your requirement "that each step should only ever see the state of the world when the previous step has finished".
Do you mean that the TestContext should always only flush it's values to the next step only if the previous succeed? A little bit of STM? How is success defined? Just no exception thrown or a special successful assert-method call as in your example?