3.20.4. Collecting components (technical names) from the AUT
Prev | 3.20. Object mapping | Next

### 3.20.4. Collecting components (technical names) from the AUT

Once your test specification is ready, you can collect components (technical names) from the AUT to map (assign) to the component names you used in your tests.

To collect components from the AUT, you must have:

- started and connected to the AUT Agent (Section 3.2, “Starting and connecting to the AUT Agent”)

- created a Test Case containing Test Steps (Section 3.12.2, “Creating Test Cases”)

- added Test Cases to a Test Suite (Section 3.16, “Working with Test Suites”)

- specified an AUT (Section 3.7, “Defining applications under test (AUTs)”)

- configured an AUT (Section 3.8.1, “Configuring AUTs to be started from the ITE”) if you want to start the AUT from the ITE

- chosen an AUT for the Test Suite (Section 3.16.2, “Configuring Test Suites in the Properties View”)

- started the AUT to be mapped (Section 3.21.2, “Starting the AUT”)

- opened the object mapping editor (Section 3.20.2.1, “Opening the Object Mapping Editor”)

1. Start the Object Mapping Mode by clicking the arrow next to the Start Object Mapping Mode on the toolbar and selecting which AUT (based on the AUT ID) you want to map.

   | If you have the same AUT running more than once, you will only be able to collect components from the AUT whose ID you chose. The object map for AUTs that are the same is, however, identical.

   The status bar will show that the Object Mapping Mode is active.

2. Bring the AUT into focus by clicking on its titlebar.

3. Collect the component as described in the sections below for the specific toolkits.

4. In the Object Mapping Editor, the technical name for this component will appear in the unassigned technical names area.

   | If you have already mapped this component, it will be highlighted in the Object Mapping Editor.

5. When you collect a technical name, it is displayed with a colored dot in the Object Mapping Editor. The color of the dot indicates the strength of the component recognition for this component, in the current state of the AUT (Section 3.20.4.2, “Understanding the colored dots when collecting component names in the Object Mapping Editor”).

6. Collect all the names you need from the AUT and then click the Stop Object Mapping Mode button on the toolbar.

7. You can now map (assign) the component names you used in your Test Cases to the technical names you have collected from the AUT Section 3.20.5, “Mapping (assigning) collected technical names to component names”.

#### 3.20.4.1. For Java AUTs:

- In the AUT for which the Object Mapping Mode was started, move the cursor over components. They will be highlighted with a green border (see Figure 3.29, “Green Border around Supported Component”).

  | Due to technical limitations in the JavaFX-Toolkit it might be that a component is not highlighted even though you can map it.

- To collect a technical name for a component, hover the cursor over the component whose name you want to collect.

- Press »CTRL+SHIFT+Q«.

  | You can change the key combination for the object mapping in the object mapping preferences (Section 3.29.8, “Object mapping preferences”). This is a good idea if the current key combination has a specific meaning in your AUT. You can also set the object mapping combination to a mouse click if your AUT does not accept key combinations.

- If no component is collected, then you may need to write an extension to recognize and test the component. More information on this is available in the Developer Manual.

#### 3.20.4.2. Understanding the colored dots when collecting component names in the Object Mapping Editor

When technical names are collected from the AUT, they appear in the Object Mapping Editor with a colored dot. The color of the dot corresponds to the strength of the component recognition for this component at the time of collecting.

A green dot

  signifies that the component can be found as an exact match, and that only this component was above the threshold (Section 3.20.2.4, “The configuration view in the Object Mapping Editor”) (i.e. only this component was considered as possible.

A yellow dot

  means that the component can be found as an exact match, but that other components were also above the threshold, i.e. this was not the only component considered possible.

A red dot

  means that the component can not currently be found if a test is executed. The recognition value for the component is below the current threshold.

You can use this information to identify components that will not be recognized in the current state of the AUT before running the test.

| The colored dot disappears after saving. It is not a measurement of the component state over time, but only at the moment when the component was collected. You can see how well each component was actually located during a test by looking in the test result reports. Each Test Step provides information on the match heuristic for each component.