Object Brower : annoying behavior

Question

Hi everyone !I have a very annoying issue. Sometimes, the object browser load the DOM in the same manner than "legacy features".The normal behavior is this :Custom Angular components are properly detected, like "AppSignRoot" in this example.But sometimes, the tree look like this :Custom components are not properly detected. Here, the "AppSignRoot" node is "Panel(4)".If I hit the refresh button, everything gets back to normal like the first screenshot.But, calling the Refresh() method on the page object or browser object (in my script and / or test item) does nothing.&nbsp;The DOM is randomly not detected properly.&nbsp;And I'm out of solutions.Any idea ?

rraghvani · Answer

I've seen this issue a number of times in the past, and it's relating to Chromium (used by Chrome and Edge) not exposing the controls to TestCompletes' Object Spy engine. If you are using the Supported Browsers, then you shouldn't have this issue.&nbsp;
Chrome and Edge automatically updates in the background to ensure users have access to the latest features, security updates, and performance optimisations. This usually causes breakages in other application that depend on it. Hence, supported browser is usually a few versions behind.
I can only suggest to open a support ticket via https://support.smartbear.com/testcomplete/

eykxas · Answer

That's precisely the problem. It appeared with version 140 of the engine. Unfortunately, my company enforces extremely strict security rules, and I can't revert to a previous version (it's strictly forbidden by internal policy).

I'm stuck and need to find a workaround. I tried using Firefox, but that would require rebuilding the entire project, which isn't feasible (not to mention the significant performance drop).

I'll open a ticket, meanwhile, if you have any idea...

rraghvani · Answer

Unfortunately, there’s no workaround for this. By the time SmartBear addresses the issue, Chromium will likely have updated its engine several times, causing TestComplete to break again.
Chromium has a massive development team compared to SmartBear, making it impossible for SmartBear to keep pace with daily changes. That’s why SmartBear specifies supported browser versions in their requirements.

hassan_ballan · Answer

Switching to Firefox&nbsp;does not require rebuilding the project—TestComplete supports cross-browser testing, so you can record in one browser and run in others. (Supported Browsers, Cross-Browser Testing)
For Chromium DOM recognition issues, Refresh() doesn’t help, but you can catch the condition and send an F5 key programmatically (Sys.Browser("Chrome").Keys("[F5]")) to refresh and continue.
🤖 AI-assisted response👍 Found it helpful? Click Like✅ Issue resolved? Click Mark as Solution

eykxas · Answer

That's not how our project works. It doesn't use a lot of built-in functions of TC, instead, the project relying on a custom set of tools (coded in javascript). Directly "mapped" onto the DOM structure exposing by chromium engine.This DOM structure is not the same in firefox engine, that means all of our Xpath and associated classes need to be modified or rewrited.&nbsp;And, the performance of firefox is way too slow. (Plus, I forgot to mention that our project is not approved for firefox).

Forum Discussion

Object Brower : annoying behavior

7 Replies

Recent Discussions

Unable to run Keyword Tests after 15.80

"Simplified WPF object tree" setting

'ADO' is not defined error - TC v15.79

Related Content

License check behavior

Testcomplete behavior

Inconsistent Keys Method Behavior