Where do you go from here?

Now that you have learned how to use UFT, including creating automated GUI tests, automated API tests, and tests running both GUI and API tests, you are ready to use UFT to test your own application.

We suggest that you use the following procedure when testing your own application.

  1. Analyze your application.

    • Determine the development environment. This enables you to load the relevant UFT add-ins and provide support for the objects in your application.
    • Determine the business processes that users will perform. Plan your tests and actions accordingly.
    • Decide how to organize your test and which operations to include. Consider the goals of the test, and confirm that your application and UFT are set to match the needs of your test.

    At this stage, you can begin creating the skeletal tests and actions to use when testing your application.

  2. Prepare your testing infrastructure.

    Decide how to store the objects in your test. You can store the objects for each action in its corresponding local object repository, or you can store the objects for each action in one or more common (shared) object repositories. You can also use the same shared object repository for multiple actions.

    • If you are new to testing, you may want to use a local object repository for each action. This is the default setting, and all objects are automatically added to the local repository of each action.
    • If you are familiar with testing, it is often most efficient to work with shared object repositories, which can be used for one or more actions. Object information is kept in one central location, and when the objects in your application change, you can update them in that one location for multiple actions, in multiple tests.

    Although not discussed in this tutorial, you can also export test objects from a local object repository to a shared object repository, and you can merge object repositories.

    You may also want to create function libraries to enhance UFT functionality.

    For details, see the Unified Functional Testing User Guide.

  3. Build your test.

    While you create your test steps, follow the steps you expect users to perform as they navigate within your application.

  4. Enhance your test.

    • Add checkpoints to search for specific values of a page, object, text string, or table cell.
    • Replace fixed values in your test with parameter to check how your application performs the same operations with multiple sets of data.

    You can further enhance your test with programming, conditional, and loop statements, which add logic to your test. For details, see the Unified Functional Testing User Guide.

  5. Debug your test.

    Debug your test to check that it operates smoothly and without interruption. For details, see the Unified Functional Testing User Guide.

  6. Run your test.

    Run your test on your application to check that the application functions as expected.

  7. Analyze the run results.

    Examine the results of your test to pinpoint defects in your application. (Refer to the appropriate sections of this tutorial to understand what to look for in the run results for checkpoints or parameters.)