My experience is that using the old Selenium APIs with WebDriver 2.0 is about 100% slower (i.e., execution takes twice as long).
On Mon, Jul 18, 2011 at 1:40 PM, Mark <[email protected]> wrote: > It looks like Selenium 2.0 can run using WebDriver where it directly > works with the browser or emulating the older Selenium RC approach. > Is WebDriver slow or is it when you try to run 2.0 using the older > style tests? I thought part of the point of WebDriver was to be > faster. > > Mark > > On Mon, Jul 18, 2011 at 1:47 PM, Howard Lewis Ship <[email protected]> wrote: >> I've been using Geb (a Groovy wrapper around Selenium 2.0) and I've >> been having a lot of trouble since Selenium 2.0 changes things; just >> swapping out the new code takes a huge hit on performance. I might >> take a go at this, but I'd rather start thinking in terms of >> deprecating the selenium support inside tapestry-test and seeing about >> adopting Geb as a better solution that embraces Selenium 2.0. >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
