|WebDriver vs. WebDriverBackedSelenium||Marcel Overdijk||7/18/11 2:22 PM|
I'm using the WebDriverBackedSelenium myself as I prefer the Selenium
API over the WebDriver API.
I also read somewhere that WebDriver is the way forward for Selenium
so I was wondering what that will mean for the
WebDriverBackedSelenium / Selenium API in the future.
I'm starting a new project and I can still choose any option.
What would you recomment?
|Re: [selenium-developers] WebDriver vs. WebDriverBackedSelenium||David Burns||7/19/11 1:43 AM|
For a new project I would go straight to Webdriver. The WebdriverBackedSelenium is a stop gap to help users migrate to webdriver at their own pace.
On Jul 18, 2011 10:29 PM, "Marcel Overdijk" <marcelo...@gmail.com> wrote:
|Re: [selenium-developers] WebDriver vs. WebDriverBackedSelenium||Daniel Wagner-Hall||7/19/11 3:25 AM|
The WebDriverBackedSelenium is significantly slower than using either
the Selenium API directly, or the WebDriver API directly.
|Re: [selenium-developers] WebDriver vs. WebDriverBackedSelenium||susanth b||9/4/12 12:56 AM|
Hi Daniel Wagner,
As you said WebDriverBackedSelenium is not using either Selenium API or WebDriver API , then how it works?
|Re: [selenium-developers] WebDriver vs. WebDriverBackedSelenium||Patrick Lightbody||9/4/12 10:30 AM|
WebDriverBackedSelenium provides Selenium 1.x compatible interfaces but is implemented using 100% WebDriver.
--To view this discussion on the web visit https://groups.google.com/d/msg/selenium-developers/-/gG9kw18wTp8J.
|Re: [selenium-developers] WebDriver vs. WebDriverBackedSelenium||susanth b||9/4/12 8:37 PM|
Here the conclusion Webdrivbacked selenium has all the similar method names of Selenium RC but its developed using WebDriver and Weblement classes .
There is no browserbot dependancy in WebdriverBacked Selenium.
It helps to convert existing RC project to Webdriver.
The methods in the Webdrivbacked selenium can also be used in the your project reusable library insted of writing methods such as type,click etc.. using Webdriver and WebElement methods.
Thanks and Regards
|Re: [selenium-developers] WebDriver vs. WebDriverBackedSelenium||Simon Stewart||9/21/12 4:54 AM|
There's a number of reasons why we recommend against using the
webdriver-backed selenium on a new project:
1) It's slow: it has to try and implement the same behaviour as the
original Selenium RC. This means that it performs a host of additional
commands for every action that are often not needed, but _might be_ in
2) It's slow. I think this point is worth repeating.
3) Almost all development effort right now is being focused on the
webdriver API. This is the one that's being supported by the browser
vendors themselves, and this is the one that's the focus of the W3C
work. If you find a bug in the webdriver code, we're likely to try and
fix it. If you find a similar bug in the rc code, or the
webdriver-backed selenium, given the amount of effort being expended
on it, it's unlikely that your issue will be fixed.
4) Aesthetically, I prefer the webdriver API. I am, of course, biased.
5) The WebDriver APIs have a host of useful support classes and
utilities that make it easier to do common tasks. You can use these
with the webdriver-backed selenium, but you'll be constantly
unwrapping the underlying webdriver instance. Ugh.
On Thu, Sep 6, 2012 at 12:50 PM, CS <csin...@gmail.com> wrote:
> Hi Daniel.
> Could you please elaborate more on why "WebDriverBackedSelenium" is slow?
> Though, underneath it uses only WebDriver API, why is it advised not use
> "WebDriverBackedSelenium" for a new project?
>> > --
>> > To post to this group, send email to selenium-...@googlegroups.com.
> --> https://groups.google.com/d/msg/selenium-developers/-/wQTuvMsEzkIJ.