-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
DeveloperMode requirement is a roadblock for QA. #975
Comments
As an alternative I recommend: |
You could tweak the registry entry: https://www.tenforums.com/tutorials/30136-turn-off-developer-mode-windows-10-a.html otherwise you'll have to investigate another stack, FlaUi is newer than TestStackWhite but both accomplish the same goals if you don't want to use the native com. |
Thanks. We heavily looked into CodedUI for a while, but microsoft really dropped the ball on it. FlaUI seems like it is derived from that and I am intrigued, but we have too much invested into Selenium to make the jump. |
Has anyone discovered a work around for the Developer mode Requirement? This is a bit of a blocker. Thanks! |
vote! |
Practically, this driver is of no use if this restriction is not removed. |
If you're not remotely executing anything, FlaUI is a phenomenal alternative |
Developer mode is a blocker for testing any application. Users dont use any application in developers mode, so to actually test in same environment as users, developer mode should be removed. I guess developer mode is because properties are accessible to winappdriver only through developer mode. This is kind of blocker and should be changed to similar way as selenium webdriver accesses the web elements. |
It was said that this was an artificial requirement imposed to ensure operational security.
However, QA is testing the User experience and if users aren't running in Developer Mode than QA isn't allowed to test in it either. It has been viewed as an unacceptable change in the testing environment by every QA manager I have spoken with, which is a shame as I rather not fall back on Winium or (shudder) TestComplete.
The text was updated successfully, but these errors were encountered: