[
http://jira.codehaus.org/browse/JBEHAVE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Hammant resolved JBEHAVE-429.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.2
Assignee: Paul Hammant
> @AfterScenario should execute in reverse order to @BeforeScenario
> -----------------------------------------------------------------
>
> Key: JBEHAVE-429
> URL: http://jira.codehaus.org/browse/JBEHAVE-429
> Project: JBehave
> Issue Type: Bug
> Reporter: Paul Hammant
> Assignee: Paul Hammant
> Fix For: 3.2
>
>
> Consider WebDriver situations, where the order below is nearly always going
> to be the case:
> new PerStoriesWebDriverSteps(..),
> new PerStoriesContextView(..),
> new WebDriverScreenshotOnFailure(..)
> If we change from PerStoriesWebDriverSteps to PerScenarioWebDriverSteps, then
> we have a problem. PerScenarioWebDriverSteps could conceivable drop the
> reference to WebDriver after closing it, and cause
> WebDriverScreenshotOnFailure to fail when it's needing to leap into action.
> The reproduction involved making steps fail, and making the
> PerStoriesWebDriverSteps to PerScenarioWebDriverSteps change.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
