Mapping Web Elements With Extended Find Enabled

How Web Objects Are Mapped

Examples

The following web objects are always added to Name Mapping:

• Objects that the test interacts with (regardless of the tag name). For example, objects that you clicked during the test recording.

• Objects with the following ObjectType (see Web Object Types Used by Web and Hybrid Mobile Applications):

  Applet     Article Aside

  Canvas     Details Figure

  Footer     Form Frame

  Header     Math Nav

  Object Section SVG

• Objects with a non-empty role attribute other than presentation.

• ExtJS objects with the following class names:

  x-accordion x-boundlist x-btn x-color-picker

  x-datepicker x-fieldset x-form x-grid-checkbox

  x-grid-view    x-panel x-progress x-slider

  x-tab x-tab-bar x-timepicker    x-toolbar

  x-tree-panel x-tree-checkbox x-window

Intermediate container objects that do not fit the above categories, such as DIVs and TABLEs with no role, are added to Name Mapping only if they are needed for unique identification of their child objects (see the examples below).

Note that the id and name attributes do not affect whether a web object will be added to Name Mapping. Only the object’s type (tag name) and the role attribute matter. For example, to make sure a specific DIV or TABLE will be added to Name Mapping during the test recording, ask the application developers to assign a non-presentational role to it.

Objects whose one or more parent objects are omitted from the Name Mapping hierarchy automatically get the Extended Find attribute enabled. TestComplete can also set the Extended Find attribute for some other objects to compensate for possible parent hierarchy changes.

Below are examples of web pages, Name Mapping files generated after recording tests against these pages and an explanation of why some objects were included or not included into Name Mapping.

Web Page	Name Mapping	Comments
Show HTML Show HTMLHide HTML HTMLCopy Code <div id="nav">   <p><a href="/">Home</a></p>   <p><a href="/products">Products</a></p>   <p><a href="/support">Support</a></p> </div>		The Panel (div) object was not auto-mapped, because it does not fit the above-mentioned categories.
Show HTML Show HTMLHide HTML HTMLCopy Code <div id="nav" role="navigation">   <p><a href="/">Home</a></p>   <p><a href="/products">Products</a></p>   <p><a href="/support">Support</a></p> </div>		The Panel (div) object was auto-mapped, because it has a non-presentational role - navigation.
Show HTML Show HTMLHide HTML HTMLCopy Code <div>   <form>     <table>       <tbody>         <tr>           <td>             <input type="button" value="Send">           </td>         </tr>         <tr>           <td>             <input type="button" value="Receive">           </td>         </tr>       </tbody>     </table>   </form> </div>		The Panel, Table and Cell objects were not auto-mapped, because they do fit the above-mentioned categories and are not needed for the Button object identification.
Show HTML Show HTMLHide HTML HTMLCopy Code <div>   <form>     <table>       <tbody>         <tr>           <td>             <input type="button" value="Send">           </td>         </tr>         <tr>           <td>             <input type="button" value="Send">           </td>         </tr>       </tbody>     </table>   </form> </div>		This example is similar to the previous one, except the buttons are the same. The Name Mapping here includes the Table and Cell objects, because they are needed to uniquely identify each of the buttons.