Name Mapping for web application testing.
Historically, many web application testing projects have been written using name mapping. And during tests, name mapping often stops working. Here is an example of 6 test cases. I run 2 functions thr...
Forum Discussion
I imagine this is caused due to timing. We could quickly test this by adding a hardcoded delay, and if that solves the problem, optimize the delay by making it dynamically wait for an object to be visible, enabled or exists.
No, I completely disagree with you. Because these are the same functions. 5 times successfully worked out. Always fail 6 times. Even if all these vehicles are mixed.
I think that in the course of work some internal cache of Test Complete overflows because of what Name Mapping ceases to see web elements.
HI Tank302
Its very difficult to say without seeing it on a call.
The error you have attached can be solved by what mattb suggests as it could be linked to wait times.
That being said there can be other ways to solve this issue as there could be other root causes too!
This 3 part video shows you how to commonly solve the error "the object does not exist"
pt1
https://www.youtube.com/watch?v=v4MayIKY-mA
pt2
https://www.youtube.com/watch?v=-JBSP9fVxFc
pt3
https://www.youtube.com/watch?v=z3Q8YJUahcg
You can explore more in our documentation here https://support.smartbear.com/testcomplete/docs/testing-with/running/handling-errors/object-not-found/unable-to-find-object.html#:~:text=If%20developers%20have%20changed%20the,an%20alias%20to%20access%20it.
If the issue persists, reach out to your SmartBear account manager and they can arrange a call with an engineer
KR
Vinnie
Hi,
> some internal cache of Test Complete
You also might to meet Aliases caching case described in this help article: https://support.smartbear.com/testcomplete/docs/reference/test-objects/members/common-for-all/refreshmappinginfo-method.html
