Remapping Issues. Inconsistencies.
I have a question that have been bothering since I started using TestComplete in August. This issue seems to come back more and more often. Hi all! Happy New Year! We have couple of website...
Forum Discussion
Thanks for the fast reply and explanations!
I am new to TestComplete so I am still learning.
So the way i fix the issues I double click on the object inside of the keyword test and then click on "Drag the target to point to the object" and then i bring the mouse to the right field to grab it.
Now whats weird to me, if I hit on "highlight" even before fixing anything, TestComplete highlights the right field, so it "knows" that that's the field, why would not it click on it during the actual test?
Also I remapped the first name field using the "drag the target to point to the object" and then I looked at the name of the object starting with "NameMapping.sys..." and after I remapped it, it did not change, but it does the trick and fixes the problem during the test run. (see screenshot). So am I actually changing the properties of an actual object by using this method or remapping the object itself. I am lost, sorry with so many confusing questions.
OK, so, there may be a couple of problems.
Problem 1 may be a timing issue where the objects might not be present on screen or recognized before TestComplete times out. Using extended find as you are doing, while it's really a VERY useful feature, does slow down object recognition. So, during test run, TC might not have enough time to find the object. You can resolve this by increasing the Auto-wait Timeout setting under Tools -> Current Project Settings -> Playback
Problem 2 might be the following:
The object identification problems MIGHT not be with the text field itself but with the parent objects that I have indicated (or others that aren't visible on screen). formCCv3, if any of it's properties changed might be the culprit... or that footer one... or something else.
Brief intro to nameMapping engine... to identify an object, it starts at the root of NameMapping.Sys. So, if you have something like
NameMapping.Sys.browser.myPage.footer.frame.textbox
if you are trying to use textbox, TestComplete does the following:
1) Check child objects of Sys to see if there is a browser
2) If there is a browser, check child objects of browser for any page that matches the property settings of myPage
3) If myPage is found, check child objects of myPage to for any object that matches the property settings of foot
4) if footer is found, check child objects of footer for any object that matches the property settings of frame
5) if frame is found, check child objects of frame for any object that matches the property settings of textbox
6) if textbox is found, perform the indicated operation
If at any step Testcomplete fails to find what it's looking for, it will fail the whole operation and you'll get an "object not found" error of some sort.
So, in your situation, if any of those parent objects are changing, that could "break" your textboxes. The solution is to examine those objects and see if there are properties that you can apply to them that won't break as easily.
That makes it more clear. :smileyhappy:
Thanks a lot for all suggestions.
Most likely its a problem 2.
