Home
Test Author Guide
This guide describes how to create test scripts in HCL OneTest™ Performance and enhances tests by applying different test elements such as dataset, variables, and verification points. This guide is intended for testers.
Compound tests
You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.
Creating a compound test
You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.

Test Author Guide
This guide describes how to create test scripts in HCL OneTest™ Performance and enhances tests by applying different test elements such as dataset, variables, and verification points. This guide is intended for testers.
- Creating tests
  To create a test, you record representative interactions with an application.
- Editing tests
  After you record a test, you can edit it to include datasets (to provide variable data rather than the data that you recorded), verification points (to confirm that the test runs as expected), and data correlation (to ensure that returned data is appropriate for the corresponding request). You can also add protocol-specific elements to a test. When you edit a test, the modified items appear in italic type. The italic type changes to regular type after you save the test.
- Compound tests
  You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.
  - Creating a compound test
    You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.
  - Viewing compound tests
    You can view a compound test in the Compound Test Editor.
  - Adding tests into a compound test
    After creating a compound test, you can add the smaller test pieces that contribute to the larger workflow you are constructing with the compound test. When you run a compound test, each of the tests added to it are invoked in the sequence defined.
  - Modifying a compound test
    You can modify a compound test in the Compound Test Editor.
  - Running compound tests
    When you run a compound test, its test elements are run in the order defined in the compound test.
  - Generating compound test result reports
    When a compound test run is completed, a Test Log is shown in the Test Execution perspective. You can work with the information in the test log and also generate test result reports.
  - Adding a compound test to a Test Workbench project
    You can create a compound test in a test workbench project. If you have an existing compound test, you can import the test to a test workbench project.
  - Adding compound tests to schedule
    To test the performance of multiple tests, you can add all the tests to a compound test and add the compound test to a user group or a rate runner group. When you run a schedule, all the tests in the compound test are run in a sequential order.
- Simulating services with stubs
  Service stubs enable you to simulate the behavior of an actual service for a wide variety testing or integration purposes.
- Sending service requests with the generic service client
  The generic service client enables you to send requests to services for which you do not have a convenient client and to view the responses returned by the service.
- Emulating workloads
  You emulate a workload by creating a schedule and adding user groups/rate runner groups, tests, and other elements to it.

Creating a compound test

You can create compound tests to help you organize smaller tests into scenarios that can then be run end-to-end. You can combine tests from different extensions to achieve end-to-end flow.

Procedure

Create a test workbench project.
In the Web UI Test perspective, in the Test Navigator, right-click the test workbench project and click New, and then click Compound Test.
In the New Compound Test dialog box, specify the name of the compound test and the location where it must be stored. By default, the test is stored in the workspace of the test workbench project you selected. You can select a different project location if desired.
The file extension testsuite is added to the file name, and the new compound test is added to the Compound Tests folder of the test workbench project, visible in the Logical View. The new test is also visible in the Resource View, under the test workbench project. The contents and test element details are displayed in the compound test editor in the right panel.
In the compound test editor, add the components of the compound test.

The types of tests you can combine into a compound test depend on the testing requirements and on the components that you have licensed. For example, if you have the appropriate licenses, you can add Web UI tests, performance tests, mobile web tests, and functional tests into a compound test.
To build the scenario you require in a compound test, you can also add the following annotations by clicking Add and selecting the appropriate option:
- Comments
- Synchronization points
- Loops
- Delays
- Transaction folders
- Tests that are mandatory, using the Finally blocks
- Tests to be run in random order, using the Random Selector
Save your changes.