Hi,
the FluentWebDriverPage is simply a fluent-based facade using a
FluentWebDriver. The underlying WebDriverProvider is the same as a
non-fluent page and is injected in the constructor.
The PerStoryWebDriverSteps should use exactly the same underlying
WebDriverProvider (autowired via some dependency-injection mechanism),
so if the provider end() method is invoked you shouldn't need to do
anything else.
Are you experiencing or noticing a particular problem? If so, could you
share a project that reproduced it?
Cheers
On 29/07/2014 19:14, Emanuel Campolo wrote:
Hi all !
I've added the jbehave-web module to a personal project where I use
testng. I'm using the FirefoxWebDriverProvider to manage the webdriver
instances, taking advantage of the ThreadLocal for multithreaded tests.
My question is, even though I call the end() method every time a test
completes to remove the driver assigned to the current thread, i don't
know how to the same thing to the FluentWebDriver (a thread local
variable that the FluentWebDriverPage has).
I noticed that , for example, the PerStoryWebDriverSteps only
executes driverProvider.end() but as in mentioned above, i didn't
find any clean up for the FluentWebDriver instances that
FluentWebDriverPage creates.
Thanks in advance :)
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
