3.15.6. No component type exists message in Component Names View
Prev | 3.15. Working with component names | Next

### 3.15.6. No component type exists message in Component Names View

This situation occurs when a component name that has been propagated and then renamed at the place of reuse is no longer accessible, either because:

- the name with which the component was propagated has been changed, or

- the checkbox to propagate the component name has been deactivated.

In such situations, you will see the message in the Component Names View :

No Component Type Exists!.

| Saving the Test Case will remove the message, however, you may want to take steps to transfer the component name before removing the message.

- An example of a situation where this occurs:

  1. You have a Test Case TC1 that has a component name propagated from it: nn_nn_grc.

  2. You reused the TC1 Test Case in another Test Case called TC2, and renamed the component name to LoginDialog_OK_btn at the place of reuse.

  3. You then either:

     - change the component name in the original Test Case to ”LoginDialog_AnyButton_btn”,

     - or you deactivate the checkbox for propagating the component name from the original Test Case.

- In the Component Names View for the reused Test Case in TC2, you will see a warning message that the component name has no type.

  | The warning field is not editable.

- Depending on whehter you renamed the component name or removed the checkbox, you can now do one of two things:

  - If you renamed the component name in the original Test Case (TC1, then you can locate the newly propagated name in the Component Names View and enter the new name for the no longer existent component type in the new name field for the newly propagated name. This essentially points the previous component name hierarchy onto the new one.

  - If you deactivated the checkbox, or if you do not want to transfer the name as mentioned above, you can simply make any change to the Test Case and then save it. The message will disappear.