Official TestComplete documentation mentions support for WebView2 in the following release notes:
However, there’s currently no detailed documentation on how to enable or fully utilize WebView2 support—especially when it’s hosted inside a WPF application.
Since you're still in a trial phase, I strongly recommend opening a support ticket with SmartBear and asking:
- Is full WebView2 (WPF-hosted) DOM support currently available in TestComplete?
- Are there required configurations, settings, or limitations?
- Is there a roadmap for improved or full support in upcoming releases?
🔗 SmartBear Support Portal
Be sure to clearly describe your setup (WPF app embedding WebView2) and mention your TestComplete version (e.g., 15.69+).
- Enable UI Automation and MSAA:
Go to:
Tools > Current Project Properties > Open Applications > UI Automation / MSAA
This may help expose more of the accessibility tree for the embedded content.
- Enable WebView2 Remote Debugging (if possible):
If your dev team can launch WebView2 with the flag:
--remote-debugging-port=9222
…then external tools (and possibly TestComplete via scripting) might connect to and inspect the internal DOM.
- Ensure the Web Testing module is active
Double-check that the “Web Testing” plugin/module is enabled in your TestComplete installation.
- Test against a minimal WebView2 sample app
This helps isolate whether the issue is with TestComplete’s capabilities or something app-specific (e.g. custom rendering or composition layers).
🤖 AI-assisted response
👍 Found it helpful? Click Like
✅ Issue resolved? Click Mark as Solution
