|
||||||||
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 Sebastian, thanks for the example!
I can see what you're trying to acheive but in this particular case I don't think it's relevant. The main goal of having a TestContext is to avoid mutable global state, which can be altered externally and therefore is not guaranteed to be how you left it at any given time. Your example still relies on a global mutable variable, albiet instantiated by a DI framework.
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.
Good luck with your prototype! Thanks.