[jbehave-dev] [jira] (JBEHAVE-1035) DelegateWebDriverNotFound: WebDriver has not been found for this thread.

[Otto Diesel (JIRA)]

Title: Message Title

Otto Diesel created an issue   JBehave / JBEHAVE-1035 DelegateWebDriverNotFound: WebDriver has not been found for this thread. Issue Type: Bug Affects Versions: web-3.5.5, 4.x Assignee: Unassigned Components: Core Created: 28/Jul/14 6:53 AM Fix Versions: 4.x Priority: Critical Reporter: Otto Diesel There seems to be a bug in 4.0-beta-8 concerning the usage of GivenStories. If I have a story which uses "GivenStories" then I get this exception: org.jbehave.web.selenium.DelegatingWebDriverProvider$DelegateWebDriverNotFound: WebDriver has not been found for this thread. Please verify you are using the correct WebDriverProvider, with the appropriate credentials if using remote access, e.g. to SauceLabs: -DSAUCE_USERNAME=xxxxxx -DSAUCE_ACCESS_KEY=xxx-xxxx-xxxx-xxxx-xxx at org.jbehave.web.selenium.DelegatingWebDriverProvider.get(DelegatingWebDriverProvider.java:24) at example.pages.PageObject.getDriver(PageObject.java:30) at example.pages.LoginPage.isLoggedIn(LoginPage.java:15) at example.steps.LoginSteps.userLoggedIn(LoginSteps.java:15) If I use JBehave 3.9.3 then it works as expected. You can reproduce it with this example: https://github.com/OttoDiesel/jbehave-selenium-example.git In class "example/SeleniumStories.java" change story filter to: String includes = System.getProperty("story.filter", "**/Stammdaten-Mutation.story"); It would be nice if you could fix it this week since this is the example for the second part of the paper on JBehave. Add Comment   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