- 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.
- 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 JSON data, binary data and encoded data to a more readable format to use data correlation.