Forum Discussion

tristaanogre's avatar
tristaanogre
Esteemed Contributor
7 years ago

Re: TestComplete v14. FindChild (dynamic) version of an XPath doesn't work in TC v14

OK... so... a couple of things.

1)  Technically speaking, finding by "Name" is not exactly the recommended way of finding an object.  You should be finding based upon a set of properties like ObjectType, ObjectIdentifier.  It's not an "XPath", it's a set of properties.  And, with the "Name" that you're using, as the message indicates, there are more than 1 object that matches what you're looking for.  So... you need to search differently

2) Get rid of the concept of "XPath" for the most part with TestComplete... use "NameMapping" and learn it's usage.  This is going to be, ultimately, more efficient and less error prone

3) TC 14 has had a number of performance improvements in object identification over previouse versions.  It is possible that, in doing so, it's actually corrected some inefficiencies making the "FindChild" that you're using return more objects that intended.

So.... Now that we have that established.... the problem is, generally, that you haven't been specific enough in your search parmeters for the desired object.  You need to use a more specific set of properties.

2 Replies

  • cgaie's avatar
    cgaie
    New Contributor
    7 years ago

    So basically if I use the aliases path below to identify the object the test Pass with a warning

     

    Aliases.ImageScope.HwndSource_PopupRoot.PopupRoot.Decorator.NonLogicalAdornerDecorator.MenuItem.RootGrid.MacrosListView.WPFObject("ListViewItem", "", 1)

     

    I used the FullName path below and the test Pass without any warning, as you said in the Aliases path I haven't been specific enough in the search parmeters for the desired object

     

    Sys.Process("ImageScope").WPFObject("HwndSource: PopupRoot", "", 1).WPFObject("PopupRoot", "", 1).WPFObject("Decorator", "", 1).WPFObject("NonLogicalAdornerDecorator", "", 1).WPFObject("MenuItem", "", 1).WPFObject("RootGrid").WPFObject("MacrosListView").WPFObject("ListViewItem", "", 1)

     

    Thanks

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      7 years ago

      What's the warning?  Because it could be that, in your mapping, you haven't designated a clear enough set of properties to uniquely identify the object, hence a "Ambiguous recognition" warning...  NameMapping is work... it's SUPPOSED to be work... and if you don't spend time with it... you will fail at your work.