Integrating and running performance test scripts in Micro Focus ALM
To obtain test result details, you must integrate and run performance test scripts in Micro Focus Application Lifecycle Management (ALM) by using a readily available template available in HCL OneTest™ Performance installation directory.
About this task
The performance test template is available in the installation directory of
HCL OneTest™ Performance. You must copy the contents of the template to a new VAPI-XP
VBScript test script in Micro Focus ALM, add your test script details into the VAPI-XP
VBScript test script, and then run the test script.
Note: You can use
Micro Focus ALM client only on Microsoft™ Internet Explorer. For more information, see Micro Focus ALM system
requirements.
Procedure
-
Navigate to the directory HCL\HCLOneTest\alm in HCL OneTest™ Performance
installation directory.
You can use PT_ALM_Windows.txt file for performance test scripts.
- Copy the contents of the template.
- From Micro Focus ALM, create a blank VAPI-XP Vbscript test script.
- Paste the content of the template to the VAPI-XP Vbscript test script.
-
Enter the test details in the VAPI-XP Vbscript test script by referring to the following
table:
Parameter Description Workspace Required. The complete path to the Eclipse workspace. Project Required. The path, including the file name of the project relative to the workspace. TestsuiteName Required. The path, including the file name of the test to run relative to the project. IMSharedLocation Optional. The complete path to HCLIMShared location. Varfile Optional. The complete path to the XML file that contains the variable name and value pairs. Configfile Optional. The complete path to a file that contains the parameters for a test or schedule run. ResultsFile Optional. The name of the result file. The default result file is the test or schedule name with a time stamp appended. OverwriteResultsFile Optional. Determines whether a results file with the same name is overwritten. The default value is true, which means the results file can be overwritten. Quiet Optional. Turns off any message output from the launcher and returns to the command shell when the run or the attempt is complete. Users Optional. For a schedule, the default value is the number of users specified in the schedule editor. For a test, the default value is one user. Overrides the default number of users, if required. VMArgs Optional. You can use this parameter to pass Java™ virtual machine arguments. DatasetOverride Optional. For a test or schedule, the default value is the dataset specified in the test editor or schedule editor. Overrides the default dataset value to run if required. Note:You must use the Dataset Override option to replace the dataset values during a test or schedule run. You must ensure that both original and new datasets are in the same workspace and have the same column names. You must also include the path to the dataset.
For example,
/project_name/ds_path/ds_filename.csv:/project_name/ds_path/new_ds_filename.csv.You can swap multiple datasets that are saved in a different project by adding multiple paths to the dataset separated by a semicolon (;).
For example,
/project_name1/ds_path/ds_filename.csv:/project_name1/ds_path/new_ds_filename.csv;/project_name2/ds_path/ds_filename.csv:/project_name2/ds_path/new_ds_filename.csvExportStatsFile Optional. The complete path to a directory that you can use to store exported statistical report data. ExportStatReportlist Optional. A comma-separated list of absolute paths to custom report format files (.view files) that you can use to export statistical report data with ExportStatsFile. ExportStatsHtml Optional. The complete path to a directory that you can use to export web analytic results. The results are exported to the specified directory. You can analyze the results on a web browser without using the test workbench. UserComments Optional. You can add text within the double quotation mark to display it in the User Comments row of the report. - Run the VAPI-XP Vbscript test script.