I have setup a WebRunnerApplication to make it easy to FindSteps in our domain
specific implementation of JBehave. This works fine.
However, if I go to RunStory within the WebRunnerApplication and attempt to run
a Seleniumm Test, I get errors such as below:
Given I log into ##Removed- MyApp## as user <username> with password <password>
|username|password|
|david|##Removed-password##|
Example: {username=david, password=##Removed-password##}
Given I log into RC2.0 as user david with password ##Removed-password## (FAILED)
(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.)
BTW, I am not running with Sauce Labs, I am running locally with a
SeleniumConfiguration and a simple PropertyWebdriverProvider with the system
property browser set to "firefox". This exact code (configuration() and
candidateSteps()), in an embeddable in the same project works fine.
I am creating/setting the driverProvider in the configuration() override of the
WebRunnerApplication, before returning the SeleniumConfiguration that uses it.
I have tried everything and cannot get it to find the WebdriverProvider.
Is what I am attempting possible (Webdriver from WebRunnerApplication)?
Has anyone else done anything similar and/or seen this problem before?
BTW, I am running JBehave Web 3.3.4.
Thanks.
David
The information contained in this email message and its attachments is intended
only for the private and confidential use of the recipient(s) named above,
unless the sender expressly agrees otherwise. Transmission of email over the
Internet is not a secure communications medium. If you are requesting or have
requested the transmittal of personal data, as defined in applicable privacy
laws by means of email or in an attachment to email, you must select a more
secure alternate means of transmittal that supports your obligations to protect
such personal data. If the reader of this message is not the intended recipient
and/or you have received this email in error, you must take no action based on
the information in this email and you are hereby notified that any
dissemination, misuse or copying or disclosure of this communication is
strictly prohibited. If you have received this communication in error, please
notify us immediately by email and delete the original message.
