UFT support tip: Considerations working with Java add-in
1) After installing the Java Add-in, Java applets and applications will always open with Java support active. You can confirm that your Java environment has opened properly by checking the Java console for a message similar to the following confirmation message: "Loading Unified Functional Testing Java Support (version x.x.x.x) (<App> version x.x.x.x)." (Where <App> is IE, IBM, or Oracle).
2) The Object property can access only public methods and properties. A recommended alternative to using the Object property is to extend UFT support for the required Java object using UFT Java Add-in Extensibility. For details, see the HP UFT Java Add-in Extensibility Developer Guide.
3) You cannot add SWT-based JavaMenu objects directly to an object repository using the Add Objects to Local button in the Object Repository window or the Add Objects button in the Object Repository Manager. If you want to add an SWT-based JavaMenu objects to the object repository, you can use the Add Objects or Add Objects to Local button to add its parent object and then select to add the parent object together with its descendants. Alternatively, you can add a JavaMenu object using the Navigate and Learn option in the Object Repository Manager. For details, see the section on adding test objects using the Navigate and Learn toolbar in the HP Unified Functional Testing User Guide.
4) If you want to use a control's native property for object identification, you can add the property to a Java test object as an identification property in the Add/Remove Properties Dialog Box dialog box. If you do this, consider the following:
A) You can add only native properties for which the control has a public get or is method that returns the property value.
B) If the native property name includes upper-case letters, then in the corresponding identification property name that you create, you must replace each of the upper-case letters except the first one with _<lower-case letter>. For example, to use the native property OneSmallProp, add an identification property named One_small_prop.
For more details on adding identification properties, see the section on the Object Identification dialog box in the HP Unified Functional Testing User Guide.
5) In early releases of QuickTest, Java identification properties were not case-sensitive. If you learned a test object in a QuickTest version earlier than 11.00, you need to re-learn the object with properties that are case-sensitive by performing an Update Run (using the Update test object descriptions option). For details, see the section on Updating Test Object Descriptions in the HP Unified Functional Testing User Guide.HP Unified Functional Testing (12.00) Page 197 of 549
6) In UFT, table data is always loaded from the application itself, even if the Active Screen contains an image of the table. For this reason, you must first open the table in the application before creating a table checkpoint in a test.
A) In some cases you may have to scroll to the last row of the table to make sure that all the data
B) It is not necessary to open the table in your application to edit an existing table checkpoint.
7) If you load or unload an add-in that is displayed as a child of the Java add-in in the Add-in Manager, only applications that are opened after loading or unloading the add-in are affected.
😎 When working with tests, if you create a checkpoint on an SWT-based Java tree with columns,
a table checkpoint is created.
You can find this details in the UFT Add-ins guide: http://support.openview.hp.com/selfsolve/document/KM00763116 from page 197 to 198
If you find this useful, mark Kudos.
Note: The Opinions expressed in my post are mine alone, and do not reflect the opinions of my employer. No warranties express or implied for any answered posted.