2.3. Exporting the Object Map in the ITE
Prev | Chapter 2. Writing UI tests via client API | Next

## 2.3. Exporting the Object Map in the ITE

Figure 2.3. Object Mapping Editor export function

In order to create an executable CAP instance (see Section 2.4, “Creating CAP instances”) you require a valid org.eclipse.jubula.tools.ComponentIdentifier instance. To get that, you need to

1. Start the ITE, open the project and the Object Mapping Editor for the AUT you wan't to export the Object Map for. (Or, if you are starting from scratch, firstly create a new project and do the object mapping there.)

2. Select technical names or categories you want to export(or none if you want to export all) and choose "Export Object Mapping for use in API" from the context menu of the editor as shown in Figure 2.3, “Object Mapping Editor export function”.

3. Decide whether you wan't to use a plain properties file or a Java class with static fields. Both formats will then contain all necessary information (one mapping for each mapped logical component name) to address the UI widget when the test gets executed.

4. Place this resource on the classpath of your test project.

5. If you're using the properties file format you can load the mapping and its identifier by using MakeR.createObjectMapping(...).get("logicalComponentName"). Otherwise you can simply access the static fields of the exported class.

You can also get an encoded ComponentIdentifier directly to the clipboard. This is useful if you want to replace an existing ComponentIdentifier in the API. Simply select the technical name and choose "Copy Component Identifier to clipboard" from the context menu of the editor.

| Currently the structure and information used to address a component (the mapping value itself) is not part of the API itself. Hence you still have to maintain this information within the ITE.