Home
Rational® Performance Tester
Test Author Guide
This guide describes how to create test scripts in Rational® Performance Tester 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.
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 correlation rules overview
You can use the data correlation rules editor to customize how data is correlated. You can control how references and substitutions are generated in tests, and store these rules so that you do not have to manually correlate data in every test that you record against a particular application.
Viewing data correlation rule usage
To see a record of all the elements that changed when data correlation rules are applied, open the data correlation rules log. You can use the data correlation rules log to determine which rules worked and which did not.

Rational® Performance Tester
- Release Notes
  This document contains information about what's new, installation instructions, known issues in IBM® Rational® Performance Tester and contact information of IBM Customer Support.
- System Requirements
  This document includes information about hardware and software requirements for IBM® Rational® Performance Tester.
- Getting Started
  This guide provides an overview and describes the task flows to get you to start with Rational® Performance Tester. This guide is intended for new users.
- Tutorials
  This section contains the tutorials which explains the main features of Rational® Performance Tester.
- Samples
  This section describes about the sample project which can be used with Rational® Performance Tester to test the functionality of an application.
- Administrator Guide
  This guide describes how to install Rational® Performance Tester. After you install the product, you can perform administration tasks such as license configuration and integration with other products. This guide is intended for administrators.
- Test Author Guide
  This guide describes how to create test scripts in Rational® Performance Tester 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 correlation overview
        A request can include data that was returned in the response to a previous request. Associating data in this manner is called data correlation.
      - Viewing data correlation
        You can switch between viewing all test elements in the test editor and viewing only elements related to data correlation in the test editor. Viewing only data correlation elements makes it easier to add and remove substitutions.
      - Data correlation rules overview
        You can use the data correlation rules editor to customize how data is correlated. You can control how references and substitutions are generated in tests, and store these rules so that you do not have to manually correlate data in every test that you record against a particular application.
        Creating data correlation rule sets
        To use rules-based data correlation, you must create a data correlation rule set. Data correlation rule sets are also known as rules files.
        Creating a reference using data correlation rules
        You can create a data correlation rule that creates a reference from a regular expression when the rule is applied to test data.
        Creating a substitution with data correlation rules
        You can create a data correlation rule that creates a substitution from a regular expression that is applied to test data.
        Example: Linking references to substitutions with rules
        You can create data correlation rules to link references to substitutions.
        Example: Linking substitutions to references with rules
        You can create data correlation rules to link substitutions to references.
        Example: Linking substitutions to built-in data sources with rules
        You can create data correlation rules to link substitutions to built-in data sources. Built-in data sources include the dynamically calculated variables such as Current Date, Random Number, and Timestamp.
        Recorrelating data with rules
        After you have created a data correlation rule set, you can recorrelate data in tests.
        Recording tests with data correlation rules
        After you have created a data correlation rule set, you can record a test that uses those rules.
        Generate data correlation rules in the test editor
        Instead of writing rules in the rules editor, you can generate rules automatically based on data correlation adjustments that you make while editing tests.
        Viewing data correlation rule usage
        To see a record of all the elements that changed when data correlation rules are applied, open the data correlation rules log. You can use the data correlation rules log to determine which rules worked and which did not.
      - Test data sources overview
        Use the Test Data Sources window to add or change data correlation for any supported test element.
      - Reference or Field Reference overview
        A Reference, which is in response data, points to a specific value that you want to use in a subsequent test location, generally a request. Whereas a Field Reference points to an entire block of test data.
      - Correlating multiple fields in a test
        Some tests are structured in such a way that you must correlate data for multiple fields.
      - Guidelines for adjusting data correlation
        When you run a test, you might notice that the server is not under the expected load or that your database is not being updated as expected. Incomplete or incorrect data correlation can cause these problems.
      - Finding data correlation errors
        You can use the Potential Correlation Errors view to find missing or incorrect data correlations.
      - Disabling data correlation
        You can disable a data correlation source or a substitution site. When you disable a data source, none of the substitution sites that use the source will be correlated when you run tests. When you disable a substitution site, only that specific substitution site is disabled. Other substitution sites that use the same reference will be correlated when you run tests. You can also disable data correlation entirely for subsequent tests that you record.
      - Recorrelating test data
        If you disabled automatic data correlation before recording a test, you can regenerate the test with automatic data correlation enabled.
    - Data transformation
      You can transform HTTP application specific data such as JSON data, binary data and encoded data to a more readable format to use 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.
- Test Execution Specialist Guide
  This guide describes tasks that you can perform on schedules, test execution with custom code, and Extending Rational® Performance Tester to support other protocols. This guide is intended for testers or test execution specialists.
- Test Manager Guide
  This guide describes how to keep track of the performance of the application by evaluating the test results. This guide is intended for test managers.
- Troubleshooting Guide
  This guide describes how to analyze and resolve some of the common problems that you might encounter while you work with Rational® Performance Tester.
- Reference Guide
  This guide describes, additional topics to gain more knowledge about Rational® Performance Tester.
- All Guides (PDFs)
  You can find the link to view or download the content of the release notes, system requirements, and persona guides of Rational® Performance Tester as a PDF file.
- Security Considerations
  You can take certain actions to ensure that your installation is secure, customize your security settings, and set up user access controls.
- Notices
  This document provides information about copyright, trademarks, terms and conditions for the product documentation.

Viewing data correlation rule usage

To see a record of all the elements that changed when data correlation rules are applied, open the data correlation rules log. You can use the data correlation rules log to determine which rules worked and which did not.

About this task

The Data Correlation Rules Log view opens automatically when you apply data correlation rules to a test.

Procedure

In the Data Correlation Rules Log view, consider the following options:
- You can apply data correlation rules when you record a test, or you can recorrelate existing test data. To learn more about recorrelating test data, see Recorrelating data with rules.
- You can specify the logging level in the data correlation rules file, or on the Data Correlation and Transformation wizard page.
- You can use the Action log level to debug data correlation rules. If the Action log level does not provide enough data for troubleshooting, use the Detail log level.
- You can view the data correlation actions in the chronological order. Click the Chronological log view icon to view test elements that are created or removed by the data correlation rules.
- When you are sure that the data correlation rules that you wrote work correctly, use the None or Summary log levels to reduce memory, disk-space consumption, and unnecessary entries in the error log.
Expand the first element of the log, and navigate to the detail that you want to see. Use the icons in the upper-right corner of the view to navigate through the log. For example, to navigate to the corresponding element in the test editor, select a log entry, and then click Go to test element.