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.
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.
Data transformation
You can transform HTTP application specific data such as binary data and encoded data to a more readable format to use data correlation.
Transforming GraniteDS or BlazeDS data
To test an application that is developed on Granite Data Services (GraniteDS) or Adobe BlazeDS framework, you must deserialize or transform the objects that are encoded in the AMF format to the XML format.

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.
  - Editing HTTP tests
    After you record a test, you can edit it to include variable data rather than the data that you recorded and can include verification points to confirm that the test runs as expected. You can also edit the test to include [NB1] transactions, conditional processing, custom code, and standard header or custom header to a request or response.
  - Editing SAP tests
    After you record a test, you can edit it to include variable data (rather than the data that you recorded) and verification points (to confirm that the test runs as expected).
  - Editing Citrix tests
    After you record a test, you can edit it to include variable data (rather than the data that you recorded), verification points (to confirm that the test runs as expected), transactions, conditional processing, and custom code.
  - Editing service tests
    After you record a service test, you can edit the calls and message returns to include variable data (rather than the data that you recorded). You can add verification points (to confirm that the test runs as expected), transactions, conditional processing, and custom code.
  - Editing Socket tests
    Improve the Socket tests by adding test elements.
  - Editing Kerberos tests
    You can change the Kerberos realm, user name, and password when editing tests.
  - Adding test elements
    You can add a variety of elements to a test, such as transaction blocks, IF-THEN conditions, loops, and comments.
  - Searching within tests
    Search request data or response content by right-clicking in the data or content and selecting Find. To search for specific element types and to display the results in a table, click Select. For a still more powerful search and replace, use the Test Search function.
  - Exporting a test
    To share the test scripts with manual testers or reviewers who do not have the workbench, export the test scripts to text files. You can export one file at a time.
  - Copying test assets with dependencies
    You can export test assets, and then import them into another project or workspace without losing any dependencies. Test assets include projects, schedules, and tests. You can export and import test assets to collaborate with other testers.
  - Disabling portions of a test
    When you disable portions of a test, you can still see the disabled portion, but it is not executed during a run. You can also disable portions of a schedule by using the following procedure.
  - Running test elements in random order
    You can record multiple user scenarios in a test and then run each scenario in a random order. To do this, you put each scenario under a random selector and then select the proportion of time that the scenario should be run.
  - Renaming test assets
    As your test assets increase and become more complex, you might want to rename them. Use the Eclipse Rename function or save the assets under a different name.
  - Deleting test assets
    As your test assets grow and become more complicated, you might want to delete the assets that you no longer use.
  - Debugging custom code for tests and compound tests
    If you have custom code added to a test or a compound test, you can debug the custom code for any errors by clicking the Debug button.
  - Providing tests with variable data (datasets)
    You can produce more realistic tests by changing them to use datasets. During execution, a test that uses a dataset replaces a value in the recorded test with variable test data that is stored in the dataset. This substitution allows each virtual user to generate a different request to the server.
  - Test variables
    A test variable is a user-defined, name-value pair that stores and refers to information throughout a test and between tests.
  - Correlating response and request data
    For a test to run correctly, a request that is sent to a server might need to use a value that was returned by a previous request. By ensuring that this data is correlated accurately, you can produce better performance tests.
  - Data transformation
    You can transform HTTP application specific data such as binary data and encoded data to a more readable format to use data correlation.
    - Viewing binary data
      You can view binary data in tests. Use the binary editor to inspect test data, to determine if the binary data is of interest or should be transformed so that it can be correlated. You can also edit binary data in tests. To edit binary data you need to have in-depth knowledge of the data format in question. Typically, you do not edit binary data in tests.
    - Viewing or transforming GWT encoded data
      When you record an application that is developed on Google Web Toolkit(GWT), the recorded data is encoded. To view the encoded data, open the test editor. You can also transform the encoded data into XML format, which you can use for data correlation.
    - Transforming GraniteDS or BlazeDS data
      To test an application that is developed on Granite Data Services (GraniteDS) or Adobe BlazeDS framework, you must deserialize or transform the objects that are encoded in the AMF format to the XML format.
    - Transforming SAP Web DynPro XML to ASCII
      To test applications that are built using the SAP Web DynPro framework and correlate data, you must transform data to the ASCII format.
    - Creating custom data transformations
      You can create your own data transformations to transform binary data in tests. Data transformations can convert binary data to a more readable format and can assist with data correlation.
- 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.
- 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.

Transforming GraniteDS or BlazeDS data

To test an application that is developed on Granite Data Services (GraniteDS) or Adobe BlazeDS framework, you must deserialize or transform the objects that are encoded in the AMF format to the XML format.

Before you begin

HCL OneTest™ Performance supports GraniteDS 2.3.2.
For GraniteDS transformation, you must add the lt-granite.jar and granite.jar to the class path, along with any other JAR files that are required for the deserialization process.
For BlazeDS, you must add the JAR files that are required for the deserialization process to the class path. To add lt-granite.jar or any other JAR files to the class path perform the steps as follows:
1. Right-click the project in the Test Navigator view, and then click Properties.
2. Click the Libraries tab, and then click Add External JARs.
3. Browse to PathToTheProduct\IBMIMShared\plugins\com.ibm.rational.test.lt.datatransform.adapters_VersionNumberPathToTheProduct\HCLIMShared\plugins\com.ibm.rational.test.lt.datatransform.adapters_VersionNumber to select lt-granite.jar or to any other folder to select other JAR files.
You must set the JAR files and ensure that you have the following order by clicking the Order and Export tab:
1. JRE.
2. Plug-in Dependencies.
3. lt-granite.jar.
4. Any Application JAR files.
5. BlazeDS JAR files if you use BlazeDS. For instance, flex-messagin-common.jar and flex-messaging-core.jar.
6. granite.jar.

Procedure

To transform the GraniteDS or BlazeDS data:

Record the test.
On the toolbar, click the Re-correlate test and transform data icon.
Click the Convert Granite Data Service (AMF) to XML check box and click Finish.
The AMF data is transformed to XML.

What to do next

You can now correlate the data.