Closed dotnetprofessional closed 5 years ago
Webdriver.io is much better supported and I recommend switching to it.
Alternatively, use Selenium in front of the IE driver, as it will translate protocols for you.
Thanks but the we've already built all our infrastructure around this library for mobile and we'd like to make use of it for our Web based tests as well (ie basically the same tests for all platforms). I didn't notice you had another issue tracking this #547. Is this likely to be resolved anytime soon?
There's no one actively maintaining this project at the moment, so I'm not sure how soon it will be resolved. The quick fix is to run your tests through Selenium instead of the IE driver directly.
I'm doing my best to get things back into a usable state, no promises.
On Tue, Sep 11, 2018 at 4:16 PM Jonathan Lipps notifications@github.com wrote:
There's no one actively maintaining this project at the moment, so I'm not sure how soon it will be resolved. The quick fix is to run your tests through Selenium instead of the IE driver directly.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/admc/wd/issues/553#issuecomment-420457607, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAUGBgYmM9vWI8bYyJC19_4GtjiTrvPks5uaEQxgaJpZM4WkQek .
I'm in the process of trying to get IE 11 to work with WD. However, its failing, and I've tracked it down to what appears to be a lack of support for the new W3C protocol. I noticed in the code there is some mention of this support however, I didn't see any reference this this:
The data being returned by the IE driver has this new constant, but the WD client only understands the older .ELEMENT. Modifying the code manually did get to use this new Id did get me past my initial issues, but then other parts were broken too. So I suspect this is a larger change than one spot in the callback.js file.
It seems webdriver.io has this support, as they check for both.