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. - Test data sources overview
Use the Test Data Sources window to add or change data correlation for any supported test element. - Selecting a reference in a response
When a response contains multiple matches for the regular expression that defines a reference, you can select which match is used subsequently as the data source. You can specify a particular occurrence, or you can specify a random occurrence. - 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. - Activating secure storage of dataset passwords for test automation
Starting from 9.2.0.1, you can store the encrypted dataset passwords in the Eclipse secure storage location on the computer. Now, when you run the tests from the command line, the product automatically uses the password and completes the test run. Prior to 9.2.0.1, you could not run the tests from the command line with encrypted datasets. - Exporting report counters automatically
You can change the test preferences so that report counters are automatically exported at the end of a run. This option is useful when you run a schedule from the command line because you can automatically export results without opening the workbench. - Task flow Integrating HCL OneTest UI and HCL OneTest API
You can execute integration tests in HCL OneTest™ UI by using HCL OneTest UI Extension for HCL OneTest API. In HCL OneTest UI, you can create a compound test to run the integration tests by using agents. - Resource Monitoring Service
When you apply load to a system under test, the system's resources are consumed increasingly. If the capacity of the resources does not match the load, you will notice performance degradation in the results. With the Resource Monitoring Service, you can continually observe the health of the system's resources. - Starting Resource Monitoring Service
You must access the Resource Monitoring web UI to perform the resource monitoring operations such as adding the data sources, counters, and viewing the live performance statistics. - Adding data sources to the dashboard
To monitor the resources, you must first add them to the Resource Monitoring Service web UI. For example, if you want to view the throughput, requests rate, and CPU usage of the Apache server, you must add it as a data source. - Resource Monitoring Agents