SOATest Not Working Properly on Wndows 11

Speedy993

I created a number of small SOATest regression tests to automate the process to verify our Java WebSphere applications are not broken after a major deployment of updates to these applications. These are used by our QA team with SOATest 2021.2 running on Windows 10 laptops. I created these on a Windows 10 virtual desktop and everything has been working as it should. Recently we received new Windows 11 laptops and now the tests are not running. The Edge browser opens but does not navigate to the URL for the application. The browser opens but just sits there with nothing happening. The URL is not populated in the browser. I have confirmed that the Edge Edge browser is current as is the Edge web driver.
Eventually the test will time out with this error message:
**
Error Message:
(Edge 134.0.3124.93) Unable to complete navigate action due to an unexpected error. View details
for more information.

Additional Details:
session not created: probably user data directory is already in use, please specify a unique value
for --user-data-dir argument, or don't use --user-data-dir
(Driver info: msedgedriver=134.0.3124.83
(b4ff70c9d7db212f42957ada8e4071aa6a23a4a0),platform=Windows NT 10.0.22631 x86_64) (WARNING: The
server did not provide any stacktrace information)
Command duration or timeout: 16.58 seconds
Build info: version: '2.53.1', revision: 'a36b8b1cd5757287168e54b817830adce9b0158d', time:
'2016-06-30 19:26:09'
System info: host: 'HCPxPEHf5X1WKjQ', ip: '10.0.0.136', os.name: 'Windows 10', os.arch: 'amd64',
os.version: '10.0', java.version: '1.8.0_302'
Driver info: org.openqa.selenium.edge.EdgeDriver
**

Let me know if you need anymore info or anything else. Any suggestions would be appreciated.
Thanks!

Matt Love

Support for Windows 11 was added in SOAtest 2022.1. See the release notes at https://docs.parasoft.com/display/SOA20242/SOAtest+Virtualize+and+CTP+20221
Are you able to upgrade to a newer version of SOAtest?

benken_parasoft

Build info: version: '2.53.1'

This is the version of the Selenium library which is quite old and obsolete. Upgrading to a current supported release of SOAtest will likely fix things for you.

benken_parasoft

Driver info: msedgedriver=134.0.3124.83

I also noticed MS just released Edge 135 (stable channel).

Speedy993

Thanks benken_parasoft!

We do have SOATest 2024 in house now and are moving to it from 2021. I guess in this instance we will have to move a little faster. We have a large base of SOATest 2021 tests that are used in our automated build, deploy and test processes. It is a little like trying to turn a large ship: it does not happen quickly.

Speedy993

More information about this. I have a Windows 11 laptop and connect via Citrix Workspace to a Windows 10 computer where I do all of my development. I am able to run both SOATest 2021.2 and SOATest 2024.2 on the virtual Windows 10 without any issues. I have been doing this for a number of years. The Windows 11 laptop is mainly used for running Outlook, Teams, etc. The production support group only have Windows 11 laptops and are unable to run the SOATest tests that are for the Java web apps. The test that do not run web apps seem to work fine (message broker, database, etc). I then installed both SOATest 2021.2 and 2024.2 on my Windows 11 laptop and get the same results as the production support team. The browser will open but not navigate to the URL and will eventually time out with an error.

For SOATest 2021.2 the error message is:
Error Message:
(Edge 135.0.3179.85) Unable to complete navigate action due to an unexpected error. View details
for more information.
Additional Details:
session not created: DevToolsActivePort file doesn't exist
(Driver info: msedgedriver=135.0.3179.85
(578105711aca34d1535878df51b6c326f4f264be),platform=Windows NT 10.0.22631 x86_64) (WARNING: The
server did not provide any stacktrace information)
Command duration or timeout: 60.99 seconds
Build info: version: '2.53.1', revision: 'a36b8b1cd5757287168e54b817830adce9b0158d', time:
'2016-06-30 19:26:09'

For SOATest 2024.2 the error message is:
Error Message:
(Edge 135.0.3179.85) Unable to launch Microsoft Edge. View details for instructions.
Additional Details:
Could not start a new session. Response code 500. Message: session not created: DevToolsActivePort file doesn't exist
Host info: host: 'HCRKHCHCQENOET5', ip: '172.27.35.57'
Build info: version: '4.25.0', revision: '8a8aea2337'
System info: os.name: 'Windows 11', os.arch: 'amd64', os.version: '10.0', java.version: '21.0.5'
Driver info: org.openqa.selenium.edge.EdgeDriver
Command: [null, newSession {capabilities=[Capabilities {browserName: MicrosoftEdge, ms:edgeOptions: {args: [], extensions: []}, proxy: Proxy(manual, http=localhos...}]}]
Used msedgedriver version 135.0.3179.85 at C:\Program Files\Parasoft\SOAtest\2024.2\plugins\com.parasoft.ptest.libs.web_10.7.1.202410281200\root\browsers\webdriver\edge\windows\x86\msedgedriver.exe

Doing a lot of searching on the web, all of what I found pertains to Selenium but I think the issue is similar or the same. These posts are talking about that either the webdriver and browser versions don't match (I have made sure that mine do) or that for some reason the webdriver can't be launched, such as not enough rights.

Could this be an issue of not having the authorization to run the tests? On my Windows 10 virtual computer I have administration rights. The Windows 11 laptop is locked down tightly.

Any suggestions would be helpful. At some point the virtual machines will be moved to Windows 11. Hopefully full administrator rights will be part of it.

Thanks!

benken_parasoft

Doing a lot of searching on the web, all of what I found pertains to Selenium

Yes. SOAtest happens to use Selenium WebDriver APIs. The "Response code 500" would be the HTTP error response returned by the msedgedriver. The test failure detail shows the error message as returned by Selenium's API.

These posts are talking about that either the webdriver and browser versions don't match

In your case, they do match. SOAtest gets the browser version independently, showing "Edge 135.0.3179.85". The error detail from Selenium shows "Used msedgedriver version 135.0.3179.85".

I should mention that the newer version of Selenium used by SOAtest 2024.2 will download webdrivers automatically. Unlike earlier versions of SOAtest, you no longer need to manually download and copy webdrivers into the SOAtest installation. If you already copied a "msedgedriver.exe" into the SOAtest installation then you can delete it to make Selenium download the correct one automatically. Selenium will store webdrivers in your user profile (home directory) under a ".cache/selenium" folder.

Could this be an issue of not having the authorization to run the tests?

Edge playback works without running as administrator. We have many users on Windows 11.

Any suggestions would be helpful

Since the error and behavior is not specific to SOAtest, you can often find help by searching for such errors on the web.

I found a couple things describing how different security policies can block access and what to do about that:
https://github.com/MicrosoftEdge/EdgeWebDriver/issues/109
https://learn.microsoft.com/en-us/microsoft-edge/webdriver-chromium/?tabs=c-sharp#developer-tools-availability-policy

I found a couple other suggestions recommending to first try killing any running or background instances of Edge with taskkill /f /im msedge.exe.

Speedy993

Thanks benken_parasoft! The second link in your reply provided the answer for me. The RemoteDebuggingAllowed policy was set to false in Windows 11 Edge for me and that seems to prevent SOATest from using Edge for the web tests. I am also prevented from changing this in the WIndows Registry Editor. It took a lot of back and forth with our security staff to turn this off for my testing to confirm this fixes the issue.

benken_parasoft

Thanks for the update!

The second link in your reply provided the answer for me.

I'm going to copy the solution here. Microsoft docs provide a nice explanation about how this policy specifically impacts msedgedriver:

If your IT admin has set the DeveloperToolsAvailability policy to 2, Microsoft Edge WebDriver is blocked from driving Microsoft Edge, because the driver uses Microsoft Edge DevTools. To automate Microsoft Edge, make sure the DeveloperToolsAvailability policy is set to 0 or 1.