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 three times. It doesn't matter what their order is, but name mapping always stops working on the 6th test case.
The problem is solved if after 5 test cases close and open the browser. But this is incorrect and time consuming.
Help please.
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
Thank you very much for your help, but unfortunately nothing helped. I run the same test case 6 times and it always falls in the same place, although 5 times before it was successful.
What else could be?
Hi,
I think that as per log message, you must figure-out why TemplateGuide object appears to not exist for the sixth test. Use debugger and general knowledge of your tested application to figure this out. The reasons might be different - restarted application, changed identification parameters for TemplateGuide object, delayed creation of the object, etc. This is something that is very difficult to diagnose remotely without knowing your test code and tested application.
But personally I would put my efforts to find the reason of why TemplateGuide object disappears for the sixth test (or on six iteration).
Exactly! I can't understand why I run the same test case 5 times and namemapping stops working 6 times.
Hi,
Set a breakpoint on the line that errors out and set breakpoint to trigger on the sixth pass. Then investigate in debugger if the object exists. Try to figure out what might be the reason if the object does not exist.
Here is a screenshot below. When I run the same test case 6 times, the "Done" button is no longer visible for name mapping. Why so? Nothing changes. I just run the same test case 6 times.
