Enable your device for development – UWP app developer | Microsoft Docs
Posted by jpluimers on 2020/10/20
From [WayBack] Enable your device for development – UWP app developer | Microsoft Docs:
Run these as administrator on the command prompt to:
Enable Sideloading
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock" /t REG_DWORD /f /v "AllowAllTrustedApps" /d "1"
Enable Developer Mode
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock" /t REG_DWORD /f /v "AllowDevelopmentWithoutDevLicense" /d "1"
Needed for WinAppDriver to test applications from Selenium or Katalon
When you run WinAppDriver without it, you get this:
C:\Users>"C:\Program Files (x86)\Windows Application Driver\WinAppDriver.exe"
Failed to initialize: 0x80004005
SetCapabilities name parameters and values
Various searches for what to pass as parameters to SetCapabilities failed, but the list is right at the README, but without any mention SetCapabilities, so search engines miss it with for instance “SetCapabilities” “WinAppDriver” – Google Search that only returned these links:
- [WayBack] Remote WinAppDriver testing session stops identifying objects partway through test · Issue #433 · Microsoft/WinAppDriver · GitHub
- which mentions
newCommandTimeout
and directs to [WayBack] Desired Capabilities – Appium
- which mentions
- [WayBack1/WayBack2] use Appium to explore windows app automation
Supported Capabilities
Below are the capabilities that can be used to create Windows Application Driver session.
Capabilities Descriptions Example app Application identifier or executable full path Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge appArguments Application launch arguments https://github.com/Microsoft/WinAppDriver appTopLevelWindow Existing application top level window to attach to 0xB822E2
appWorkingDir Application working directory (Classic apps only) C:\Temp
platformName Target platform name Windows platformVersion Target platform version 1.0
–jeroen
Leave a comment