WinAppDriver hangs when creating session
See original GitHub issueHi guys,
I am automating one of our UWP apps by WinAppDriver, however, when I execute my tests, sometimes, the UWP app to be tested can be launched but the WinAppDriver hangs, so the test code are not executed anymore. From the console log in below, it seems that the session mgr gets stuck in loading MitaBroker.
SessionManager - Creating session SessionManager - WinAppDriver succeeded loading MitaBroker
Could you pls help look into this issue?
I use below code to initialize the web driver instance
DesiredCapabilities appCapabilities = new DesiredCapabilities();
appCapabilities.SetCapability("platformName", "Windows");
appCapabilities.SetCapability(“deviceName”, “WindowsPC”);
appCapabilities.SetCapability(“launchTimeout”, 5000);
appCapabilities.SetCapability(“app”, “Dolby.DAX3.UI.CS_rnnrkadb60ba0!App”);
new WindowsDriver<WindowsElement>(new Uri(“http://127.0.0.1:4723”), appCapabilities);
WindowsDriver<WindowsElement> appSession= new WindowsDriver<WindowsElement>(new Uri(app_Driver_Url), appCapabilities)`
The version of the WinAppDrive I’m using is: v0.9-beta
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top GitHub Comments
@timotiusmargo
Sorry for slow response. I’ve upgraded WinAppDriver to v1.0 and tried re-run test scenarios, I don’t meet the issue anymore.
@holphi,
Depending on the application you test, some app supports multiple instance creation for every launch (e.g. Notepad) while some simply use a single instance (Alarms & Clock). When you create a session with the given
Dolby.DAX3.UI.CS_rnnrkadb60ba0!App
appId, WinAppDriver will attempt to launch/activate it and locate the main application window if it succeed.Can you please retry the scenario using the latest Widows Application Driver v1.0-RC and share your findings?