Testing Basic Functionality of the Support Set

After you define a basic .NET Windows Forms configuration file enabling UFT to identify which test object classes to use for the different controls, and (optionally) define your test object model in the test object configuration file, you can test the existing functionality of the support set. To do this, you deploy the support set and test how UFT interacts with the controls in your environment.

To test your support set after defining the test object classes and mapping them to custom .NET Windows Forms controls:

  1. In the test object configuration file, set the TypeInformation\DevelopmentMode attribute to true, to ensure that UFT reads all of the test object class information from the file each time it opens. When you complete the development of the support set, make sure to set this attribute to false.

  2. Deploy the support set on a UFT computer by copying the files of the support set to the correct locations in the UFT installation folder, as described in Placing Files in the Correct Locations.

  3. Open UFT, load the .NET Add-in, and open a GUI test. (If the Add-in Manager dialog box does not open when you open UFT, see the Micro Focus Unified Functional Testing Add-ins Guide for instructions.)

  4. Open an application with your custom controls.

  5. Based on the mapping definitions you created, UFT can already recognize and learn your controls.

    Use the Add Objects to Local button in the Object Repository dialog box to learn your controls.

  6. If you created a test object configuration file, you can already see its effect on UFT:

    1. If you added a test object method to a test object class, you can view it using the Object Spy .

    2. You can create test steps that use the test object method that you added. (If you have not yet implemented the custom server that supports this test object method, running a such a test step will cause a run-time error.)

      In the Keyword View:

      Create a test step with a test object from a class that you modified.

      • If you added a test object method to a test object class, the method appears in the list of available operations in the Operation column.

      • After you choose an operation, the Value cell is partitioned according to the number of arguments of the selected operation, and if you defined possible values for the operation (in the ListOfValues element), they are displayed in a list.

      • The descriptions and documentation strings you defined for the test object methods are displayed in tooltips and in the Documentation column, respectively.

      In the Editor:

      Create a test step with a test object from a class that you modified. The statement completion feature displays all of the operations available for the test object, and possible input values for these operations, if relevant, based on the definitions in the test object configuration file.

      In the Step Generator:

      Create a test step with a test object from a class that you modified. The operations that you defined in the test object configuration file are displayed in the Operation list, and the descriptions you defined for the operations are displayed as tooltips.

    Note: For more information on working with these options in UFT, see the Micro Focus Unified Functional Testing User Guide.