DescriptionWith the HCL OneTest UI – Web UI plug-in for HCL Launch, you can automate the execution of tests and compound tests. HCL OneTest UI – Web UI must be installed on the target computer on which the test is run. If a test is part of HCL OneTest Performance schedule and the schedule must be run, install HCL OneTest Performance and HCL OneTest UI – Web UI in the same package group (shell-sharing).
Uploaded: 12-Dec-2022 08:10
Release NoteTest type label updated.
Uploaded: 14-Sep-2022 07:49
Uploaded: 22-Jun-2022 04:19
Uploaded: 08-Feb-2022 01:40
Release NoteImports parameter added.
Uploaded: 20-Sep-2021 06:17
Release NoteAdded new option exportreport with cmdLine.
With the HCL OneTest UI – Web UI plug-in for HCL Launch, you can automate the execution of tests and compound tests.
HCL OneTest UI – Web UI must be installed on the target computer on which the test is run. If a test is part of HCL OneTest Performance schedule and the schedule must be run, install HCL OneTest Performance and HCL OneTest UI – Web UI in the same package group (shell-sharing).
This plug-in requires version 7.0 of HCL Launch.
This plug-in requires version 10.1 or later of HCL OneTest UI – Web UI.
No special steps are required for installing the plug-in. See Installing plug-ins in HCL Launch documentation.
Execute Web UI Tests from HCL OneTest UI
|Config File||String||The complete path to a file that contains the parameters for a test or schedule run.||No|
|Custom Report Format Files||String||A comma-separated list of absolute paths to custom report format files (.view files) to use when exporting statistical report data with the – exportstatsoption.||No|
|Exported HTTP Test log File||String||The complete path to a file in which to store the exported HTTP test log.||No|
|Exported Statistical Report Data File||String||The complete path to the directory in which to store exported statistical report data.||No|
|Installation Manager Location||String||Complete path to HCL Installation Manager shared location.||Yes|
|Number of Virtual Users||String||Overrides the default number of virtual users in the run. For a schedule, the default is the number of users specified in the schedule editor. For a test, the default is one user. This option creates a new copy of the schedule that contains the specified number of users.||No|
|Overwrite Results file||Boolean||Determines whether a results file with the same name is overwritten. The default value, true, means that the results file is overwritten.||No|
|Project||String||The path, including the file name, of the project relative to workspace.||Yes|
|Quiet||Boolean||Turns off any message output from the launcher and returns to the command shell when the run or the attempt is complete||No|
|Results File||String||The name of the results file. The default result file is the test or schedule name
with a time stamp appended.
|Test Suite Name||String||The path, including the file name, of the test to run relative to the project||Yes|
|User Comments||String||Add text within double quotation mark to display it in the User Comments row of the report.||No|
|VM Args||String||Java virtual machine arguments to include in the test.||No|
|Var File||String||The complete path to the XML file that contains the variable name and value pairs.||No|
|Workspace||String||Complete path to Eclipse workspace.||Yes|
Use the HCL OneTest UI – Web UI plug-in to continuously initiate the test and compound test run from HCL Launch.
Before you begin
- Install HCL OneTest UI – Web UI version and HCL Launch agent on the computer where the tests will be run.
- Install HCL Launch server and deploy the plug-in on the server.
For information about installing HCL Launch, see its documentation.
- Install HCL Launch agent and connect it to HCL Launch server. See the documentation.
- Ensure that HCL OneTest UI – Web UI is not running.
- To initiate the mobile test runs, ensure that all the devices are set to the passive mode and the playback-ready apk files are installed.
About the task
As a tester, you might have a large number of regression tests to run on the latest build of the product. Instead of manually running the tests on every new build, you can install the latest build on the HCL Launch agent computer and let HCL Launch runs the tests for you.
After deploying the HCL OneTest UI – Web UI plug-in on the server, create the component and its processes, applications and its processes, the environments, and the resources. For information about how to create these different pieces, see HCL Launch documentation.
Procedure to create a workflow
- To create a workflow for the newly created component process, click the component process. The Tools view displays the available plug-in steps.
- From HCL OneTest Studio > HCL OneTest UI – Web UI, drag the Run an HCL OneTest UI – Web UI test step to the design space.
- Specify the properties for the step. For information about the properties, see the Steps page.
- After you configure the step properties, save the step by clicking Save.
A typical process for the HCL OneTest UI – Web UI plug-in will look like the following snapshot:
A process with multiple tests will look like the following snapshot:
If you have installed multiple products on one target machine, either in the same or different package groups, you can use a single process that includes steps from different products. You must install the plug-ins of all of the products that you want to use. The process will look like the following snapshot: