The Deploy Toolkit Support command is available in Eclipse when you select a UFT One Java Add-in Extensibility project (or elements within it) in the Eclipse Package Explorer tab.

You use the Deploy Toolkit Support command to deploy the toolkit support during the development stages. To use this command, UFT One and the UFT One Java Add-in Extensibility Eclipse Plug-in must be installed on the same computer.

This command copies the toolkit configuration file and the test object configuration file to the appropriate UFT One folders. In the toolkit configuration file, the location specified for the compiled support classes is the Eclipse workspace. The next time you run the Java application, the support you developed is available on UFT One. For more information, see Deploying and Running the Custom Toolkit Support.

The Deploy Toolkit Support command copies only the test object configuration file that is named <Custom Toolkit Name>TestObjects.xml. If you create additional test object configuration files you must copy them to the appropriate folders, specified in Deploying and Running the Custom Toolkit Support.

The Deploy Toolkit Support command validates the configuration files against their corresponding XSD files, and only deploys them if their format meets the requirements (or you specify that you want to deploy in spite of the displayed discrepancies). For information on the structure of the configuration files, see the Toolkit Configuration Schema Help and the UFT One Test Object Schema Help.

The toolkit configuration file is validated against:
<UFT_One_installdir>\bin\java\sdk\eclipse\plugins\com.mercury.qtjext.plugin.QTJavaExt_1.0.0\ToolkitSchema.xsd

The test object configuration file is validated against:
<UFT_One_installdir>\bin\java\sdk\eclipse\plugins\com.mercury.qtjext.plugin.QTJavaExt_1.0.0\ClassesDefintions.xsd

The Reload Support Configuration command is available in Eclipse when you select a UFT One Java Add-in Extensibility project (or elements within it) in the Eclipse Package Explorer tab.

The Reload Support Configuration command instructs the UFT One Java Add-in Extensibility Eclipse plug-in to update the plug-in's list of supported Java classes and test object classes by reloading:

The Reload Support Configuration command affects the following items in the New UFT One Custom Support Class wizard:

The following examples demonstrate situations that require reloading the support configuration:

The Delete Custom Support command is available in Eclipse when you select a UFT One Java Add-in Extensibility custom support class in the Eclipse Package Explorer tab.

You use this command to delete support for a specific custom class. The support class is deleted, as well as its listing in the toolkit configuration file. If you created a new test object class for this support class, it is not deleted from the test object configuration file because other support classes can use it.

If you delete the support class using the Eclipse Delete command, instead of the Delete Custom Support, you must manually remove the mapping of the custom control to this support class in the toolkit configuration file.

After deleting a support class, if you previously deployed support for this custom class to UFT One, you must re-deploy the toolkit support. This replaces the toolkit configuration file with the updated one, removing the support for this custom class from UFT One as well.

If you delete a support class that serves as the base support class for another, you must manually change the inheritance of this other class. For example: InheritedCS extends ToDeleteCS that extends BuiltInCS. If you delete ToDeleteCS, you must manually change InheritedCS to extend BuiltInCS.

You cannot remove support of a complete toolkit using the UFT One Java Add-in Extensibility Eclipse Plug-in commands. To do this you have to manually delete the toolkit configuration files from their locations in the UFT One folders. For more information, see Deploying and Running the Custom Toolkit Support.

The Add Identification Property command is available in Eclipse when you select a UFT One Java Add-in Extensibility custom support class in the Eclipse Package Explorer tab.

You use this command to add an identification property after the support class is created.

You must deploy the toolkit support for the changes to take effect on UFT One.

If you add an identification property to the test object class definition, it appears in the list of identification properties in UFT One for all test objects of this class. It is for this reason that, if you plan to add properties, you create a new test object class based on the existing one, instead of modifying an existing test object class.

To add an identification property:

1. Click the Add Identification Property button in the UFT One toolbar in Eclipse. The Identification Property dialog box opens.

   

2. Enter a name for the new identification property and click OK.

3. A confirmation box opens notifying you that in addition to adding the new identification property to the support class, the property will also be added to the definition of the test object class mapped to the supported control. This identification property will then appear in the list of identification properties in UFT One for all test objects of this class.

   Click Yes if you want to continue. (If you click No, the new identification property is discarded.)

   A support method stub for the identification property you defined, named <identification property name>_attr, is added to the support class. The method stub returns null until you implement the method to match the needs of your custom control.

4. Another message box prompts you to select whether you want the new identification property to be selected by default in checkpoints.

   After you make your selection, the new identification property is added to the test object class definition in the test object configuration file.

   If you clicked Yes, the ForDefaultVerification attribute is added to the identification property definition and set to true. Otherwise, the ForDefaultVerification is not added. (In both cases, the ForVerification attribute is added and set to true, so that the new identification property is always available for checkpoints.)

   If you add an identification property that you want to be part of the unique test object description, you have to manually define this in the test object configuration file. In the row for this identification property, between the words Property and Name add the words ForDescription="true". This adds the ForDescription attribute to the Property element and sets it to true.

   For more information, see the UFT One Test Object Schema Help.

The Add Test Object Method command is available in Eclipse when you select a UFT One Java Add-in Extensibility custom support class in the Eclipse Package Explorer tab.

You use this command to add a test object method after the support class is created.

You must deploy the toolkit support for the changes to take effect on UFT One.

If you add a test object method to an existing test object class, the new methods appear in UFT One for all test objects of this class, regardless of whether or not they are supported for these objects. In a UFT One GUI test, if you call a test object method for an object, and that method is not supported, a run-time error occurs.

Therefore, if you plan to add test object methods to support a custom control, it is recommended to create a new test object class based on the existing one, instead of modifying an existing test object class.

To add a test object method:

1. Click the Add Test Object Method button in the UFT One toolbar in Eclipse. The Test Object Method Dialog box opens.

2. Define the details of the test object method you want to add, and click OK. For more information, see Understanding the Test Object Method Dialog Box.

3. A confirmation box opens notifying you that in addition to adding new test object method to the support class, the test object method will also be added to the definition of the test object class mapped to the supported control. The test object method will then appear in UFT One for all test objects of this class.

   Click Yes if you want to continue. (If you click No, the new test object method is discarded.)

   A support method stub for the test object method you defined, named <test object method name>_replayMethod, is added to the support class. This method stub returns the error value Retval.NOT_IMPLEMENTED until you implement it to match the needs of your custom control.

   In addition, the test object method is added to the test object class definition in the test object configuration file. For information on the structure and content of this file, see the UFT One Test Object Schema Help.

The Add Event Handler command is available in Eclipse when you select an AWT-based UFT One Java Add-in Extensibility custom support class in the Eclipse Package Explorer tab.

You use this command to add an event handler to the support class after it is created.

The following options are available in the Custom Control Recording Support wizard screen when you create a new support class:

If you did not select them when you created the support class, and you want to implement them, you have to do so manually. For information on how to do this, see Supporting the Record Option.

To add event handler methods:

1. Click the Add Event Handler button in the UFT One toolbar in Eclipse. The Listener dialog box opens:

   

2. Select a listener from the list.

   If the selected listener has more than one registration method, select a method from the Registration method list.

3. Click OK.

   The listener you selected is added to the signature of the support class.

   A constructor is added to the support class (or modified, if it already exists) to call the addSimpleListener method for the listener you selected. This adds the listener to the list of listeners that need to be registered on the custom control, and specifies the methods used to register and remove it.

   Method stubs for all of the event handler methods that comprise the listener you selected are added to the support class. A comment is added to each method stub, reminding you to implement the event handler to call MicAPI.record to send a record message to UFT One. For more information, see Supporting the Record Option.