3.15.3. Entering and reassigning component names in the Component Names View
Prev | 3.15. Working with component names | Next

### 3.15.3. Entering and reassigning component names in the Component Names View

| The following section deals with entering component names in the Component Names View when you have added Test Cases from the library. For information on component names in Test Steps, see the Test Steps section (Section 3.18.2, “Specifying Test Steps”).

1. Once you have added a Test Case from the library of Test Cases (Section 3.12.3, “Creating tests from the library of pre-defined Test Cases”), you will need to enter a component name for the component you want to test.

2. In the Component Names View, you will see the old name for this component, which was given in the Test Step contained in the library Test Case. The old name is just a placeholder and should be reassigned (Figure 3.24, “The Component Names View”).

   Figure 3.24. The Component Names View

   When you enter a component name in the Component Names View, you create a new reference to a component in the AUT. This component name appears in the Object Mapping Editor to be mapped to a component in your AUT. A Test Case containing component names to be reassigned can therefore be used at a variety of different places to test different actual components. If you want to rename a component name, you can do so in the Component Names Browser (Section 3.15.4, “Renaming component names”).

3. In the new name field, enter your name for this component, e.g. MainWindow_NavigationTree_tre.

   We recommend using naming conventions for component names.

4. Press »CTRL+SPACE« to see a list of component names you have already used for this type of component.

   | You can configure how frequently the content assist in the Component Names View should open in the preferences.

5. The component name you enter here will be collected by the Object Mapping Editor when you carry out object mapping so that you can assign it to a component in the AUT.

6. Every time you want to carry out an action on this component, use this name.

| See the section on the component hierarchy for some tips on using component names in your tests (Section 3.15.9, “Understanding the component hierarchy”).