Upload and run UFT Developer tests

This topic describes how to run UFT Developer tests from 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

Run a UFT Developer test from LoadRunner Enterprise

This task describes how to run UFT Developer tests from LoadRunner Enterprise.

  1. Download the VuGen Script Converter.

    For UFT Developer tests based on NUnit or JUnit, the converter must be installed on a machine that has the same NUnit or JUnit Framework installed as the one used when creating the UFT Developer test.

    1. From the LoadRunner Enterprise navigation toolbar, click and select Download Applications.

    2. Select VuGen Script Converter and click Download.

    3. Install the script converter and run VuGenScriptConverter.exe.

    Note: VuGen Script Converter can be run from LoadRunner Enterprise host machine. To do so, select Start > All Programs > Load Runner > Tools > VuGen Script Converter.

  2. Convert the test to a VuGen script.

    You can convert a test to a VuGen script using the script converter, or convert it automatically from a command prompt.

    1. Select the test and specify a location for saving the converted script.

    2. Click Convert. The converted script is saved in ZIP format.

    3. (For a JUnit tests only) Before running the converted VuGen scripts, make sure to update the Runtime Settings > Java Environment Settings > Classpath of the Vuser group, with the JUnit path and the dependent jars. For more details on runtime settings, see Configure runtime settings.

    1. Open a command prompt, and navigate to the VuGen Script Converter folder.

    2. Type VugenScriptConverterCmd.exe, followed by the desired arguments, where:

      -s is the source path and file name.

      -o is the output path.

      -silent converts the script in silent mode (does not prompt for user input or open the folder to the created script).

      Example: VugenScriptConverterCmd.exe -s:C:\Program Files\UnitTests\nunuit.jar -o:\UnitOutputDir

    3. Select the test and specify a location for saving the converted script. Click Convert. The converted script is saved in ZIP format.

  3. Upload the converted VuGen script to LoadRunner Enterprise.

    1. From the LoadRunner Enterprise navigation toolbar, click and select Test Management.

    2. In the test management tree, select a folder in which you want to upload the script, and click the Upload Scripts button.

    3. Select the zip file created by the converter utility, and click Upload.

    For details, see Upload scripts.

  4. 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 performance tests.

  5. Run the test.

    For details, see Run performance tests.

Back to top

See also: