You are here:

Modifying the HPE ALM Integration Scripts

We provide required scripts for the integration of Eggplant Functional with HPE ALM using Eggplant Integrations for HPE ALM. For any Eggplant Functional tests you want to integrate with HPE ALM, you need to include these scripts in your test suites and configure them to run before and after your test scripts.

The required scripts are included in suites that also contain test scripts you can use to set up and test your Eggplant Integrations for HPE ALM environment. Descriptions of the suites and scripts are provided below, along with instructions for downloading the suites and modifying the scripts for your environment.

After you finish modifying the scripts as described here, see Integrating Eggplant Functional with HPE ALM for instructions to run your first test to complete the integration setup in HPE ALM.

Integration Suites and Scripts

The integration scripts for HPE ALM version 2.0 are in the Eggplant Integrations for HPE ALM v2 Sample Suites file, which is available on our downloads page. Information about how to download the file is provided in the following section, along with descriptions of the integration suites and scripts contained in the file.

eggIntegrationHPALM1.suite

This suite contains the scripts required for the integration with HPE ALM.

Setup and TearDown: These scripts are required to integrate your Eggplant Functional tests with HPE ALM. The Setup script sets variables for the connection and project information in your HPE ALM. The TearDown script then uses these variables to upload the test results and perform other setup tasks in HPE ALM.
HelperScript, step1, step2, and TestCase1: These scripts are example test scripts you can run to test that your results are properly integrated into HPE ALM.

eggIntegrationHPALM2.suite

This suite contains scripts that demonstrate how you can run multiple tests using Eggplant Integrations for HPE ALM:

SetupALMInfo and UpdateALM are similar to the Setup and TearDown scripts above. They set the variables and manage the interaction with HPE ALM.
Master, TC001Login, TC0005Activity, TC022Message, TC0035Login, TC0167Activity, TC0288Message, TC0342Login, and TC0549Message are the test scripts for running multiple tests.

Download the Suites

Download the Eggplant Integrations for HPE ALM v2 Sample Suites from the Eggplant Integrations downloads page. You need access to these suites from any computer where you will be running Eggplant Functional tests that you want to integrate with HPE ALM.

Modify the Scripts

The following instructions describe how to modify the Setup and TearDown scripts from the eggIntegrationHPALM1.suite.

Note: You can also use these instructions to modify the scripts from the eggIntegrationHPALM2.suite. In this case, you modify the SetupALMInfo and UpdateALM scripts instead of Setup and TearDown.

Modify the Setup Script

From the eggIntegrationHPALM1.suite, modify the required Setup.script file to set the following variables for your HPE ALM:

Under //Configure the eggIntegration for HP ALM info comment:
Global IntegrationHost: The hostname or IP address of the computer where the Eggplant Integrations HPE ALM is running.
Global IntegrationPort: The port number of Eggplant Integrations for HPE ALM.
Under //configure the HP ALM Authentication information:
Global ALMURL: The URL of your HPE ALM server.
Global ALMDomain: The domain of your HPE ALM server.
Global ALM Project: The project you want in your HPE ALM server.
Global ALMUser: The HPE ALM username
Global QCEncryptedPwd: The HPE ALM encrypted password (created in the Eggplant Integrations for HPE ALM as described in Generating an Encrypted Password for HPE ALM).
Under //Configure the following values as desired:
Note: When you run your test script with the Setup and TearDown scripts, Eggplant Integrations for HPE ALM creates the test plan, test lab, and test set in HPE ALM if they don’t exist.
Global ALMTestPlan: The name of the test plan you want in your HPE ALM. This name is passed to the TearDown script, which makes a hierarchy based on the path provided. You can use any value or path that you want for this.
Global ALMTestLab: This variable does the same as the ALMTestPlan, except it makes the test lab in HPE ALM.
Global ALMTestset: This variable creates a test set in the HPE ALM that can include multiple test cases.
Global ALMStatus: Leave the provided value: “NOT COMPLETED.”
Note: The following variables should work with the default settings given in the HPE ALM integration example suite, but you can modify them if necessary.
urlTimeout: This variable specifies the time allowed for the integration server to respond.
asTextLimit: This variable is the size limit for the files being transmitted to the HPE ALM.

Modify the TearDown Script

Modify the required TearDown.script by setting the executable parameter of the ServerURL variable to the path of the runscript.bat file on the Eggplant Functional computer. The default value (C:\Program Files (x86)\eggPlant\runscript.bat) should work for a standard installation on a 32-bit Windows computer.

After you finish modifying the scripts as described here, see Integrating Eggplant Functional with HPE ALM for instructions to run your first test to complete the integration setup in HPE ALM.

This topic was last updated on August 19, 2021, at 03:30:51 PM.