About the Warning
The Name Mapping project item allows you to define names for processes, windows and controls that will be used to refer to these objects in tests. Each object in Name Mapping has a set of identification properties and other settings that are used to locate the relevant object in the application under test.
One of these settings is Extended Find. It instructs TestComplete to search for the object both on a specific level of the application object hierarchy and on all levels down the hierarchy. Extended Find is usually used with objects in applications that have a dynamic object hierarchy.
If the application contains a large number of objects, object identification using Extended Find may take a long time. When this happens, TestComplete posts a warning to the test log to inform you that the current mapping settings are not optimal and can affect the overall test performance.
Resolving the Problem
To resolve the problem, you need to add more objects from the parent hierarchy of the problematic object to Name Mapping. You can do that as follows:
Select the warning in the test log and then select the Details panel.
Click the link with the object name. TestComplete will open the Name Mapping editor and select this object in the Mapped Objects tree.
Right-click the selected object and choose Show in Object Browser from the context menu.
Note: This command may take some time to complete.
TestComplete will open the Object Browser and select the corresponding object in it.
Go back to the Name Mapping editor. Now select the parent object of the problematic object and choose Show in Object Browser from its context menu.
Note the large number of intermediate objects in the object tree between the selected parent object and the one that triggered the warning. To improve the object identification performance, you need to add some of these intermediate objects to Name Mapping.
In the Object Browser, select some intermediate object that you want to add to Name Mapping.
Tip: Select an object that has some unique properties, such as a specific type or identifier.
From the object’s context menu, select Map Object.
Click Yes in the message box asking whether to use the default identification properties for this object.
(Optional.) Repeat steps 5-7 to map a few intermediate objects from lower levels of the object tree.
Go back to the Name Mapping editor. Expand the Mapped Objects tree to see the newly added objects.
Drag the problematic mapped object and drop it as a child of the newly mapped objects.
|The above actions change only the set of parent objects used for identification of the problematic object. The object’s alias that is used in tests and checkpoints (for example,
Aliases.browser.pageWebOrders.linkLogout) remains the same.
If you cannot resolve the problem and you are fine with long search times, you can disable the message using the
TimeOutWarning property of the
NameMapping scripting object.