[wtr-general] invalid element state: Element is not currently interactable and may not be manipulated(classic works fine, but webdriver is throwing this error)

2016-12-16 Thread Raja gopalan
I am running the same code in Watir-classic and WATIR 6.0.2 WATIR-CLASSIC runs without any problem, but WATIR 6.0.2 throwing this error > > [12:39:18] [ERROR] : invalid element state: Element is not currently > interactable and may not be manipulated > (Session info: chrome=55.0.2883.87) > (

Re: [wtr-general] Re: Appium:RubyWatir|webdriver approach|SafariLauncher navigates to apple.com instead of specified URL

2016-12-16 Thread Titus Fortner
I'm not very familiar with mobile testing at this point. If the platform has access to a webdriver or a selenium server, then watir will work with it. If it needs something more specialized (like appium library), then Watir will not work. I've contemplated making a library for using Watir API synt

[wtr-general] Re: Appium:RubyWatir|webdriver approach|SafariLauncher navigates to apple.com instead of specified URL

2016-12-16 Thread Ambighananthan Ragavan
@Titus https://github.com/appium/ruby_lib is only for native apps if I am correct. So currently for MOBILE WEB, there is no way to run my ruby + watir automation on simulators or real devices? On Tuesday, November 22, 2016 at 10:10:36 PM UTC, Titus Fortner wrote: > > Watir does not have its own