If we switch away from the legacy Selenium support, then it will be time to rewrite the test suites in Geb. That would be great ... but it's a huge amount of effort without a lot of payoff from the end-user point of view.
On Mon, Nov 4, 2013 at 10:54 AM, Ulrich Stärk <[email protected]> wrote: > Oh never mind. We are already at Selenium 2 but not using the WebDriver > API. Need to investigate > further. > > Uli > > On 2013-11-04 19:39, Ulrich Stärk wrote: > > I'm running into problems with Selenium where the latest versions of > Firefox aren't supported > > anymore and certain actions don't trigger the corresponding events in > Chrome (e.g. onchange when > > selecting an element in Palette's available list). > > > > Switching to Selenium 2 is going to be a major pain. It will break a lot > of the existing tests and > > from the little experience I've had with it, it is very different from > Selenium 1 and certain things > > can't even be done with it anymore. I'd therefore suggest to create a > compatibility layer to allow > > existing tests coded against SeleniumTestCase to continue to run. > > > > What do you think? > > > > Uli > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > 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
