Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Capybara, Cucumber & Remote Webdriver. How to deallocate webdriver resource?
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Rodrigo Martin  
View profile  
 More options Oct 26 2012, 11:07 am
From: Rodrigo Martin <adi...@gmail.com>
Date: Fri, 26 Oct 2012 08:07:02 -0700 (PDT)
Local: Fri, Oct 26 2012 11:07 am
Subject: Capybara, Cucumber & Remote Webdriver. How to deallocate webdriver resource?

Hello everyone!

I'm working on a setup of Grid2 + Capybara + Cucumber + Selenium Remote
Webdriver.

According to the Grid2 Docs: http://code.google.com/p/selenium/wiki/Grid2

If your tests are running in parallel, *make sure that each thread

> deallocates its webdriver resource independently of any other tests running
> on other threads.* Starting 1 browser per thread at the start of the
> test-run and deallocating all browsers at the end is *not* a good idea.
> (If one test-case decides to consume abnormal amounts of time you may get
> timeouts on all the other tests because they're waiting for the slow test.
> This can be very confusing)

*How can I deallocate the remote selenium webdriver resources using
Capybara?*

I guess it should be some code inside an *After Scenario hook*, but not
sure. I've tried playing with Capybara.page.driver , searching for a stop
or quit method, but couldn't find out a suitable method to accomplish this.

Any help would be really appreciated!
Regards! Rodrigo.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »