Hi,
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
some circumstances.
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.
Simon
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?
>
> Thanks,
> CS
> To view this discussion on the web visit
>
https://groups.google.com/d/msg/selenium-developers/-/wQTuvMsEzkIJ.