Forum Discussion

eykxas's avatar
eykxas
Regular Contributor
5 days ago

Object Brower : annoying behavior

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 ...
object recognition
eykxas's avatar
eykxas
Regular Contributor
2 days ago

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. 

And, the performance of firefox is way too slow. (Plus, I forgot to mention that our project is not approved for firefox).

rraghvani's avatar
rraghvani
Icon for Champion Level 3 rankChampion Level 3
2 days ago

Hassan’s response is based on the "answer" given by ChatGPT! Unfortunately ChatGPT doesn't know if you're using XPath or Classic testing, language, scripting or keyword test, and just assume you can easily change things 🤦🏻‍♂️

  • Hassan_Ballan's avatar
    Hassan_Ballan
    Icon for Champion Level 3 rankChampion Level 3
    2 days ago

    Thanks for the clarification.
    Just to note — my earlier response wasn’t a generic ChatGPT-style answer. It was based on the common TestComplete setups I’ve worked with, where teams use TC’s built-in object model and cross-browser execution is usually a viable option.

    My background is mainly in standard web testing with XPath, and I don’t have extensive experience with custom Angular components or frameworks that interact directly with the browser engine. So my suggestion came from the perspective of how TC typically functions out-of-the-box.

    After eykxas explained their environment — especially the custom JavaScript layer tied closely to the Chromium DOM — it’s clear that their project operates very differently from a standard TC setup. In that context, the usual cross-browser guidance understandably doesn’t apply.

    Thanks again for the additional details; they help clarify why the standard approach isn’t suitable in this case.

    If you want an even shorter version, I can condense it further.

    🤖 AI-assisted response
    👍 Found it helpful? Click Like
    ✅ Issue resolved? Click Mark as Solution