Adding test elements

You can add a variety of elements to a test, such as transaction blocks, IF-THEN conditions, loops, and comments.

Adding a comment
You can add a comment to document a test.
Adding a transaction to a test
A transaction is a specific group of test elements whose performance you are interested in. When viewing the test results, you can view performance data about any transactions that you have added.
Adding conditional logic
You can add an If-Else conditional logic around portions of a test, a compound test, or a schedule and you can make those portions of a test run when a specific condition is met. A conditional block can run portions of a test that depend on the value of a reference or field reference. The reference or field reference must exist in the test and precede the If-Else condition.
Synchronizing users in tests
By inserting a synchronization point, you can coordinate the activities of a number of virtual users by pausing and resuming activities. You can synchronize all virtual users at the beginning of a test and stagger the release times so that the users do not overload the system. Synchronization points are also useful in stress testing.
Adding a loop to a test
You can define part of a test as a loop that runs a specified number of times. If the loop contains a synchronization point, the synchronization point is released after the first iteration of the loop and stays released for all further iterations.
Adding Dataset Mapper
You can include a Dataset Mapper in a compound test or a schedule to assign the dataset values to the variables that are defined in multiple tests. In previous releases, to apply the dataset values to multiple tests, you had to associate the dataset to each test. The Dataset Mapper is able to map the dataset columns with the variables.
Adding data source controller
Use this test element to control how the data is fetched from the data sources to be used by the test. You can use data from dataset, array variables, built-in data sources, and correlation.
Controlling the flow of test
A test is usually run in the order it was recorded. However, you might want to add some conditions to the test that the users would actually face when interacting with the application under test. For example, if you select a product, you want to know its manufacturing date. If the date is not available, you want to exit. You can now add such control to the test.

Parent topic: Editing tests