[
https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272981#comment-272981
]
Adriano Bonat commented on JBEHAVE-543:
---
Unfortunately I don't know where we could setup the
I coded something guys -
https://github.com/paul-hammant/jbehave-core/commit/2195b7a4d5038d4f1f087c9f2fa7f92228430b3c-
it works in a basic way. The flaw (when using it against a large
commercial jbehave-webdriver solution) was that if the restart happened, a
new browser frame was made. If some
My tuppence-worth: I think Brian's locks would be a more expressive way
of guaranteeing what you want - you need exclusive access to
the-shared-state-which-is-inventory. This would be usefulf for other
scenarios too, I imagine. Checking for itemUnavailable() might give
false positives - e.g.
[
https://jira.codehaus.org/browse/JBEHAVE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-548:
-
Fix Version/s: 3.5
> @BeforeExample und @AfterExample
>
>
>
[
https://jira.codehaus.org/browse/JBEHAVE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272887#comment-272887
]
Dennis Becker commented on JBEHAVE-548:
---
I thought this behaviour has been implemented by th