Tahir, there is new advice on the HtmlUnitDriver wiki page for Selenium, you may want to read.
Then make a subclass of DelegatingWebDriverProvider, and override initialize() to do the right new of HtmlUnitDriver for you. Use your new subclass when you are setting up the rest of the JBehave initialization stuff. - Paul On Thu, Oct 14, 2010 at 3:57 AM, Mauro Talevi <[email protected]>wrote: > Hi Tahir, > > not really sure I understand your question and how this is related to > JBehave Selenium support. The WebDriverProvider and its impls allow > users to specify any instance of WebDriver, but that's where our > boundary lies. Which instance of WebDriver you specify is really in > your hands. Your question seems more to do with the specific instance > of WebDriver you are using and would probably be best addressed to the > Selenium folks. > > Cheers > > On 13/10/2010 22:12, Tahir Raza wrote: > > Hello Mauro, > > > > Quick question. I see that using HtmlUnitDriver (true) makes it use IE > > Javascript engine. Can we use Firefix Javascript engine with > > HtmlUnitDriver ? IS there a way? > > > > That would definitely help us ! > > > > Thanks for replying! > > > > Tahir > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
