3.18.2.3 Working with categories in the Object Mapping Editor

Default categories in the Object Mapping Editor
The Object Mapping Editor tree view displays the following categories by default:

Unassigned component names:
these are the names you have used in your Test Cases or component names that you have created 3.13.1. 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 3.18.4, 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 Jubula 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 5.3.2.

\includegraphics[height=2cm]{lightbulb} It is a good idea to create categories in the Object Mapping Editor . See the section on best practices 5.3.2 for more 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.
    \includegraphics[height=2cm]{lightbulb} If you have already mapped the technical name, the name will be shown in the Object Mapping Editor , but not moved into the category.
    \includegraphics[height=2cm]{lightbulb} The status bar displays which category you are mapping into.



Copyright BREDEX GmbH 2012. Made available under the Eclipse Public License v1.0.