Forum Discussion
Can you share what you have done already to-date? Give us a screenshot of what you have recorded.
You say it "failed". What happened? What error message did you get?
Also, review the following.
https://support.smartbear.com/testcomplete/docs/keyword-testing/basic/data-driven-loops.html
- tristaanogre6 years agoEsteemed Contributor
Generally speaking, what I'm seeing is that the problem is not in the loop itself but in the object identification for your various components.
1) You have the "Extended Find" turned on for automatic mapping. While Extended Find is a good feature, it can cause a LOT of confusion in your mapping and can increase execution time. Go to Tools | Options | Engines | NameMapping and uncheck "Use extended find when possible". This will prevent using that flag moving forward.
2) The object you have mapped as "Link" probably was mapped based upon the first item you selected. You should examine the mapping properties of that object and adjust them to be less specific to the individual item and more generic to the link on the page. You may need to do some work where you're not going to map the individual links but use a FindChild to find the desired link based upon your data driven loop.
- jawed6 years agoOccasional Contributor
Can U pls elaborate it with practical example with steps. What operation should i use from testcomplete for to find child?
- AlexKaras6 years agoChampion Level 3
Hi,
From the test log provided, it looks like the first loop iteration passed successfully and the problem occurred on the second iteration. Most probably, the root of the problem is not the error message but the warning one above the error.
'Ambiguous recognition' warning means that more than one object matching namemapping recognition criteria was found during the search.
Your practical steps may be like this:
-- Read for details the information in the Additional Info log pane for the 'Ambiguous recognition' warning;
-- Investigate your tested application with Object Browser/Object Spy and find those objects that were identified as 'link';
-- Make a decision if it is OK for your application to have more than one 'link' object at the given moment of time and for the given application state. Report an issue to development if it is not;
-- If it is OK to have more than one 'link', then investigate their properties and adjust your NameMapping so that only one required object was identified as the 'link'.
Related Content
- 9 months agoMehwishDaud
- 5 years agom_essaid
Recent Discussions
- 30 minutes agotorus
- 7 hours agomegha_phophalia
- 7 hours agomegha_phophalia