[jbehave-dev] [jira] (JBEHAVE-790) When using PerScenarioWebDriverSteps.java and GivenStories then occurs DelegateWebDriverNotFound exception

[Rodrigo Machado (JIRA)]

Title: Message Title

Rodrigo Machado edited a comment on an issue   Re: When using PerScenarioWebDriverSteps.java and GivenStories then occurs DelegateWebDriverNotFound exception Let me try to explain better, sorry about the delay to answer you. Debugging the code, I've detected that the @BeforeStories and @AfterStories were executed in main thread. This would be fine if the WebDriver implementation was not thread local. On my @BeforeStories, I start my webDriver to use the browser instance in all my stories. So, the main thread creates the webDriver. After that the code start running the stories in the configurable thread pool, so, when the stories try to get the Webdriver, the ThreadLocal Design returns null, and then we start seeing NPE's in any WebDriver call. This is why we can see the failures on the PerStoriesWebDriverSteps and not in PerStoryWebDriverSteps. This issue was not happening on 4.0-beta-9 and start happening on 4.0-beta-10. Any thoughts? Add Comment   JBehave / JBEHAVE-790 When using PerScenarioWebDriverSteps.java and GivenStories then occurs DelegateWebDriverNotFound exception When I use as life cycle steps PerScenarioWebDriverSteps and try to execute scenario which has GivenStories section then occurs DelegateWebDriverNotFound. What happens during executions: 1. Firefox blank window is opened (for top level scenario?) 2. Another firefox windows is opened and executes scenario from GivenStories section then this window is ... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email