Thanks for the update!
Just to clarify: it sounds like you're testing both a desktop app (which uses WebView2) and a web app in a browser, and the issue seems to be affecting only the web app tests.
One theory is that the desktop application’s WebView2 runtime may be interfering with TestComplete’s ability to hook into the regular browser (Chrome or IE). WebView2 can spawn shared processes (msedgewebview2.exe) that might confuse or conflict with TestComplete’s expected browser structure, especially if COM objects or injected DLLs overlap.
A few things you might try to isolate the issue:
- Run the web-based test without the desktop app running to see if the problem still occurs.
- Terminate all WebView2 processes (like msedgewebview2.exe) before launching the browser and running your test.
- If you're using TestComplete's process filtering, try excluding the desktop app’s process or its WebView2 child processes.
- You could also test the web app in a clean environment where the desktop app isn't installed, to rule out interference.
Let us know what you find — it would be helpful to confirm if the WebView2 runtime from the desktop app is the source of the conflict.
🤖 AI-assisted response
👍 Found it helpful? Click Like
✅ Issue resolved? Click Mark as Solution
