Unable to find element - relative solution
I face a problem that TestComplete stops seeing elements it interacted before. If I map them again they appears under another node of app structure. After some time TestComplete stops seeing them again and I need to re-map them again.
I would understand if that happened with new versions, but it happens even within one and the same version.
Any suggestions? What can be the problem about?
Is there any way to map desktop app elements that will not depend on code structure?
My developer says, he can add id to all elements. But I could not find any id-related methods for desktop apps.
That would help me a lot...
Solved! Go to Solution.
Moved UI Automation to the top.
Hopefully, it is what I am looking for...
p.s if you accidentally come across the article related to that, please, share the link. Thanks
Found it by going here
And searching for "Object Browser Order".
This is my go to place for looking up stuff if I don't know where to find it immediately. 🙂
[Hall of Fame]
Please consider giving a Kudo if I write good stuff
Why automate? I do automated testing because there's only so much a human being can do and remain healthy. Sleep is a requirement. So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.
Mysterious Gremlin Master
Vegas Thrill Rider