Develop a unit test using Eclipse (JUnit test)

The Eclipse Add-in for Developers lets you create a JUnit test using Eclipse.

Note:  

  • For supported Eclipse and JDK/JRE versions, see Supported Protocols.
  • The following procedure is also applicable if you are using Selenium with your JUnit test.

To create a unit test in Eclipse:

  1. Prerequisite: Make sure you have a supported JDK version installed on your machine. Go to java.com to check your version or download the required version.

    Open Eclipse and select Window > Preferences. Navigate to the Java > Installed JREs node. If the relevant version (for example, jre11) is not in the Installed JREs list, click Add and use the wizard to add its folder (for example, C:\Program Files\Java\jre11).

    In the Installed JREs list, click the check box by the relevant version to instruct Eclipse to use this version.

  2. Run the Eclipse Dev add-in, LREclipseIDEAddInDevSetup.exe, from your LoadRunner Professional installation package's Additional Components\IDE Add-Ins Dev folder. Check during installation that the displayed Eclipse path is correct.

    After installing the Eclipse add-in, rebuild the plugin cache by running the following command line string: Eclipse.exe -clean.

  3. In Eclipse, open your JUnit test.

  4. Code the test as you normally would in Eclipse.

  5. Build your Java classes.

  6. Select DevOps Vuser > Add LoadRunner API Reference to add the required functions to your script, as well as transactions, rendezvous points, and messages.

    Tip: If the DevOps Vuser menu is not visible in the Eclipse menu bar, go to the <LoadRunner Professional root>\bin folder, locate the hp.lr.continuousdelivery.eclipse42addin.jar file, and copy it to the Eclipse dropins folder.

  7. Select DevOps Vuser > Run Vuser to run the test from within Eclipse to verify its functionality.

    Tip: Check the Eclipse console log for errors, and try the following to resolve issues:

    • JDK not found. Check that Java is installed correctly.
    • JDK found, Mdrv exit code is 1. Increase the JVM heap size.
    • JDK found, logs show some package(s) can’t be found. Check that the packages exist.

  8. Once the previous step is successfully completed, use the DevOps Vuser menu to launch LoadRunner Controller, or add the test to a Controller scenario that is already open.

    Alternatively, export the project as a .jar file, then add the test to Controller as System or Unit Tests.

    Tip: When exporting as a .jar file, please export without dependent class files.

  9. The class file can be added to a scenario at any time, as a unit test. For details, see New Scenario dialog box.

    Note: If you are running multiple instances of Eclipse and you want to use the add-in for each instance, you must manually install the Eclipse Add-in for Developers for each instance. Locate the hp.lr.continuousdelivery.eclipse42addin.jar file in the <LoadRunner Professional root>\bin folder, and copy it to the dropins folder for each Eclipse instance.

Back to top

See also: