Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Selenium 4 #1839

Open
lawcrens opened this issue Dec 14, 2022 · 25 comments
Open

Support for Selenium 4 #1839

lawcrens opened this issue Dec 14, 2022 · 25 comments

Comments

@lawcrens
Copy link

Hello,

Wanted to request that WinAppDriver is supported on Selenium 4. Selenium 3 has been deprecated for a year

@pm90pl
Copy link

pm90pl commented Dec 15, 2022

What do you exactly mean by 'Selenium 4 support '? WinAppDriver implements W3 WebDriver standard. Selenium 4 is a client implementation that consumes W3 WebDriver API.

@lawcrens
Copy link
Author

I and many others have been getting an error when running WinAppDriver.

https://stackoverflow.com/questions/74632066/appium-winappdriver-and-selenium-4

https://stackoverflow.com/questions/72921159/winappdriver-reference-to-type-ifindsbytagname-claims-it-is-defined-in-webdr

https://stackoverflow.com/questions/74138893/selenium-4-not-compatible-with-winappdriver

The consensus is that WinAppDriver is not compatible with Selenium 4. If this is not the case, do you know how can this can be troubleshooted?

@DLightstone

This comment was marked as off-topic.

@PavanMudigondaTR
Copy link

I have the same question ! Please someone from Microsoft please answer !

@farnsword
Copy link

Hey everyone.
Can anyone advise if it is going to happen?
It is a kind of blocker.

@pm90pl
Copy link

pm90pl commented Jan 10, 2023

Yeah. So, the current version is not compatible with W3C WebDriver standard what makes it incompatible with Selenium 4. There is no clear roadmap for WAD and it's not open source so you have to deal it on your own.
Upgrading Selenium without checking WAD compatibility was a mistake. Sorry.

@farnsword
Copy link

Well, at this point I only need to update the selenium version to 4.0 as using the latest Chrome version requires Selenium v4, so I stuck with Chrome v95.
As a last resort - this repository is under an MIT license which allows forking and modification, so may try to build our own version of it.
Thanks for the answer.

@pm90pl
Copy link

pm90pl commented Jan 10, 2023

But this repo contains only examples, not WinAppDriver implementation.

@farnsword
Copy link

Oh my...thanks for pointing that out.
Tough luck then.

@PavanMudigondaTR
Copy link

I have this email address of Microsoft team winappdriverteam@microsoft.com

@d2a-raudenaerde
Copy link

Has anybody sent them an email yet?

@DLightstone

This comment was marked as off-topic.

@PavanMudigondaTR
Copy link

PavanMudigondaTR commented Jan 14, 2023

Sent. I request everyone to send a email. To save time you can copy and send the below.

winappdriverteam@microsoft.com

Hi WinAppDriver Team at Microsoft,

Thanks for all the great work so far!

We are looking for support for Selenium 4 Java for WinAppDriver. We would appreciate if someone could look at this thread and respond back on your plans !

#1839 (comment)

@d2a-raudenaerde
Copy link

@PavanMudigondaTR thanks for the template!. Would you please edit it and add 'Thanks for all the great work so far!' as first line? Thanks :)

@nguyenquangtay
Copy link

sent also, thanks! :)

@dmridul1827
Copy link

thanks everyone for bringing it up. I am also facing same issue while migrating winappdriver to work with Sel 4.

Any further update or resolution, anyone has? Would be grateful!

@ShinjiruPP
Copy link

ShinjiruPP commented Jun 19, 2023

Are there some updates??? About Selenium4 + WinAppDriver ??
It is blocker for the new development about Test Automation framework.

@DLightstone
Copy link

ShinjiruPP
Generally speaking I would interpret an absence of a reply to mean - no updates planed

The preferred development environment is the one that works, not the one which uses the lasted and greatest infrastructure.

This may mean having to manually test things that are not present in the old infrastructure.

@StavHayounNoiberg
Copy link

Any updates or answer from Microsoft regarding this issue?

@fastinggirl
Copy link

Any update on this?

@sunrise-soft
Copy link

sunrise-soft commented Sep 1, 2023

Hi there!
Seem this is an abandoned project :(
I just wonder does Microsoft apply test automation for their Desktop applications and if yes, which one they're using

@RamaNarasimhaChanda
Copy link

Hi All, Since we are not having update from micro soft on this . What is the alternative approach other's are using can you please share.

@daluu
Copy link

daluu commented Oct 30, 2023

Well, obviously, for this issue, I can think of 2 workarounds/alternatives:

  • don't use Selenium 4 while using WinAppDriver, until a fix is available if ever (so stay on Selenium 3 or 2, etc.). For this particular issue, if you need to use Selenium 4, maybe use dual approach and dual version dependency management. Use Selenium 4 for web/mobile automation, then use Selenium 3 for now for desktop automation, within your test framework.

  • look into WinAppDriver alternative tools (there are some), and see which of those support (1) WebDriver API/protocol, and (2) Selenium 4 version of the protocol.

There are alternative tools mentioned in various comments in #1550, and I sort of compiled a list in Accruent/robotframework-applicationlibrary#72 (comment)

@AG-QALab
Copy link

AG-QALab commented Feb 3, 2024

  • Install Nodejs and WinAppDriver
  • Install Appium 2+ version : npm i -g appium
  • Install appium windows driver : appium driver install --source=npm appium-windows-driver
  • run appium command
  • execute the scripts

Its working.

@alatriste1982
Copy link

Any update from MS on this one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests