UFT Developer tests

This topic describes how to use UFT Developer tests in LoadRunner Enterprise.

Prerequisites

Below is a list of prerequisites that are required to run UFT Developer tests from LoadRunner Enterprise.

  • Configure the load generator machine the same way as the machine that is used to record or prepare the script or test.

  • For UFT Developer tests based on NUnit or JUnit:

    Test Type Description
    NUnit
    • The same version of NUnit Framework must be installed on the load generator and on the machine used for test creation (the one installed as NuGet package). If the versions are different, errors might occur during the test run.

    • Make sure that nunit.framework.dll resides in the same directory as the NUnit test.

    JUnit
    • Make sure JDK is installed on the machine used as the load generator.

    • If your test has dependencies, verify that they are available on the load generator machine with the same paths as defined under Runtime Settings > Classpath.

    • You must have the JAVA_HOME environment variable included in the PATH variable on the load generator and Controller machines were applicable (to avoid displaying an error that Java is not installed).

  • Create a UFT Developer test, and save it on your file system.

    Note:  

    • The file path inside a script folder must not exceed 260 characters.

    • You will need to convert the test to a VuGen script before uploading it to LoadRunner Enterprise (described in the steps below).

Back to top

Convert and upload UFT Developer tests

This task describes how to use UFT Developer tests in LoadRunner Enterprise.

  1. Convert UFT Developer tests based on NUnit or JUnit test to a VuGen script.

    For details, see Scripts.

  2. Upload the converted VuGen script to LoadRunner Enterprise.

    For details, see Upload a script.

  3. Create a test using the script.

    Assign as the load generator a machine that has UFT Developer and the relevant prerequisites installed on it.

    For details, see Design a test.

  4. Run the test.

    For details, see Run performance tests.

Back to top

See also: