Jonathan Neal

We're using this keyboard library. https://github.com/charygao/MouseKeyboardLibrary/

https://github.com/microsoft/WinAppDriver/issues/1686#issuecomment-1048632954

Current 5.0 Appium is using w3c. It is a TODO for the next WinAppDriver release. To fix your problem you'll need to downgrade.

S ***@***.*** Sent from my Galaxy -------- Original message -------- From: ANUNAYA THAKUR ***@***.***> Date: 9/11/22 8:35 AM (GMT-08:00) To: microsoft/WinAppDriver ***@***.***> Cc: Jonathan Neal ***@***.***>, Mention ***@***.***> Subject: Re:...

Per @DHowett: https://github.com/microsoft/WinAppDriver/issues/1610#issuecomment-944544522 fix is in the works... But, this project had a fast start and now hasn't had any updates since. @DHowett could get us a better guess than...

From my experience with our 1 application we test... For performance: - Do not find elements from root. - .FindElement has an Enabled expectation which will fail at the implicit...

@anunay1 we set them to a variable in our class property and reset them on test cleanup. Now the number of searched through elements are reduced. This helps us because...

AppiumWebElement.FindElement() will wait for an element to exist and be enabled. AppiumWebElement.FindElement**s**() will not wait.

We made an AppiumWebElement extension for these. .Click() can easily be blocked by other elements. If you plan on only testing with 1 monitor, you can use the .Location property...

Exactly what you have, but use FindElements and Actions to click the location.