3.20.2. Working with the Object Mapping Editor
Prev | 3.20. Object mapping | Next

### 3.20.2. Working with the Object Mapping Editor

#### 3.20.2.1. Opening the Object Mapping Editor

1. Open the Object Mapping Editor by selecting the Test Suite whose components you want to map and selecting:

   Open with-->Object Mapping Editor.

   | The Object Mapping Editor also opens automatically when you start the Object Mapping Mode via the toolbar.

   The Object Mapping Editor for the AUT used by this Test Suite will appear (see (Figure 3.28, “Object Mapping Editor”)).

   | You can see the name of the AUT you are mapping in the tab of the editor.

#### 3.20.2.2. The Object Mapping Editor

The Object Mapping pane in the Object Mapping Editor is where you perform your object mapping. It contains three areas for the three main categories. IHere, you can:

- Assign (map) technical names to component names (Section 3.20.5, “Mapping (assigning) collected technical names to component names”) by dragging component names onto technical names (either assigned or unassigned).

- Create new component names for your tests (Section 3.15.2, “Creating new component names”).

- Rename component names (Section 3.15.4, “Renaming component names”).

- Create categories and map into them (Section 3.20.2.3, “Working with categories in the Object Mapping Editor”).

#### 3.20.2.3. Working with categories in the Object Mapping Editor

There are three areas in the Object Mapping Editor, corresponding to the three types of names.

Unassigned component names:

  these are the names you have used in your Test Cases or component names that you have created (Section 3.15.2, “Creating new component names”). They are unassigned because they have not yet been mapped to a technical name.

Unassigned technical names:

  these are the names that you have collected from the AUT (Section 3.20.4, “Collecting components (technical names) from the AUT”), but not yet assigned to component names.

Assigned names:

  there are pairs of names that have been mapped to each other. Each technical name can be mapped to one or more component names. This mapping tells the ITE which actual components you are referring to in your Test Cases.

Creating categories in the Object Mapping Editor
We recommend creating categories in the Object Mapping Editor to make your mapping work easier.

- You can create categories and subcategories in the assigned names area in the lower part of the Object Mapping Editor by:

  1. Selecting one of the assigned names in the Object Mapping Editor.

  2. Selecting ”create category” from the context-sensitive menu.

  3. Entering a name for the category

     | You can’t have two categories with the same name at the same level.

- When you are mapping, you can choose which category to map into. See the next Section 3.20.2.3, “Working with categories in the Object Mapping Editor” for details.

Mapping into categories in the Object Mapping Editor
Once you have created categories in the Object Mapping Editor, you can choose to map technical names collected from the AUT directly into a category. This can help if you have created a category for each dialog/window, and you want to map all of the components from it into one category.

1. When you are in the Object Mapping Mode, right-click onthe category you want to map into and select:

   Map components into this category

   to make the technical names you collect from the AUT appear in this subcategory.

   | If you have already mapped the technical name, the name will be shown in the Object Mapping Editor, but not moved into the category.

   | The status bar displays which category you are mapping into.

#### 3.20.2.4. The configuration view in the Object Mapping Editor

In the configuration view in the Object Mapping Editor you can alter the object recognition for the test execution.

Understanding object recognition
Object recognition during test execution is based on a calculation which takes various factors into account. For some applications, some factors may be more important than others, and you can change their weighting accordingly.

The object location is a heuristic process. During test execution, a calculation is made for each component in the AUT to see how similar it is to the originally mapped component. This calculation is based primarily on the component type – if you mapped a combo box, only combo boxes will considered. For each component of the same type, the similarity to the original is calculated using weighted properties. The factors used in the calculation are:

Name:

  The name of the object within the AUT code, as given by the developer (if a name was given).

Path:

  The route through the AUT hierarchy to get to this component.

Context:

  The components in the vicinity of this component.

Threshold:

  This determines what percentage value a component in the AUT must have in order to be considered as the originally mapped component. Components with a value under the threshold are not considered. The component with the highest value above the threshold is chosen during execution.

Options for object recognition You can change the profile used during test execution using the combo box:

Standard:

  This is the default profile. It has a high value for name weight and lower values for context and path. The threshold is 85%.

Strict:

  In this profile, the values for name, path and context are the same as in the standard profile. The threshold is at 100%. This means that a component must exactly correspond to the originally mapped component.

Given names:

  In this profile, only the component name is considered. A component will only be selected if it has the same name as the originally mapped component. This profile can be used when you are sure that all of the components in the AUT have unique names.

Custom:

  This profile lets you move the sliders yourself. You can lock sliders to stop them being affected by other sliders.

Figure 3.27. Object Mapping Configuration

| Take care when manually customizing the object mapping settings. You may have test execution problems if you have set the values too strictly, or not strictly enough.

| You can change the profile for individual components, please read Section 3.20.7, “Component specific Profile” for more information.

#### 3.20.2.5. Refreshing the Object Mapping Editor

1. Select refresh from the context-sensitive menu in the Object Mapping Editor or press »F5« to refresh the Object Mapping Editor.

2. Confirm that you want to want to refresh the editor.

When you refresh the Object Mapping Editor, any new component names which have been added to Test Suites for this AUT are collected.

#### 3.20.2.6. Finding components in the AUT via the Object Mapping Editor: highlight in AUT

In the Object Mapping Editor, you can search for:

- All the places where a component name has been used in the test (Section 3.30.3, “Searching for places where a component name has been used”)

- The specific place where a particular component name comes from in the test (Section 3.30.3, “Searching for places where a component name has been used”)

- The technical component in the AUT (see below).

Highlighting a component in the AUT

To search for components in the AUT, the Object Mapping Editor must be open (Section 3.20.2.1, “Opening the Object Mapping Editor”), and the AUT must be running (Section 3.21.2, “Starting the AUT”) in the Object Mapping Mode (Section 3.20.4, “Collecting components (technical names) from the AUT”).

1. In the Object Mapping Editor, right-click on the technical name whose component you want to find in the AUT and select:

   Highlight in AUT

   from the context-sensitive menu.

2. The component whose technical name you selected will be highlighted with a green border in the AUT.

   | You can only highlight components that are currently visible in the AUT.