The Clip Editor, Add drop-down menu provides the ability to easily add generic (or empty) messages, browser actions, delays, checkpoints, comments as well as all collection types to a test clip.
The Add drop-down menu includes three sections:
- The first section includes add commands for clip elements that pace and control the test: Checkpoint, Time Delay, and Control)
- The second section includes Add a Comment for test clip annotation
- The third section contains add commands for each of the supported collection types
- To add an empty container, choose a relevant Add menu command to add the item after the current selection.
For example, Choosing Add a Transaction above will insert the new empty transaction after the selected clip element-index.php (1)—as shown below in Icon view.
The Clip Editor now supports adding all collection types (e.g. Pages, Groups, Chains, Transactions, If-Then-Else, and Switch) from the Clip Editor toolbar Add menu on the Clip Editor toolbar. In an empty clip, adding an empty container from the Add menu will add the empty collection to the workspace. For clips with existing clip elements, the container will be inserted after the current selected clip element.
Each Add command is distinguished by its collection icon:
Add a Chain
Chains are user-specified groups of clip elements that behave as one unit and always play sequentially. Chains can include delays, messages, scripts and browser actions. This icon shows a chain linking two Content-Types.
Add a Group
Groups are user-specified groups of clip elements that behave as one unit but have no additional properties such as timing (they have the same timing as their containing Clip). Groups can include any item that is permitted in the containing Clip. This icon shows a cascade of content types in a single row.
Add a Transaction
Transactions provide a means to logically group and capture metrics for one or more tasks in a process.Transactions permit discrete business processes to be grouped accordingly. For example, a multi-step checkout process from an ecommerce website.
Unlike pages, which can contain only one HTML page and which treat each HTML document as separate steps in a process, a Transaction permits all the parts of a logical group to be tested together.
Add a Page
Pages model, or simulate, the way real world web pages behave. They have a top-level HTML page, which has resources, sometimes referred to in the load-testing world as “assets”.
Pages are used to gather all of the requests for a given web page or node into one container so that they can easily be understood as a “page” during testing.
Additionally, Pages include special timing and can be automatically created from recordings, or manually by user-selection. Once created, pages behave as one unit with a defined “HTML Document”.
Add an If-Then-Else
If-Then-Else containers are conditional statements that work similarly to those common in many programming languages. They provide actions to take when a predicate event occurs (the if), in which case a consequence is executed (the then), and in the absence of which (the else) an alternative action occurs.
In CloudTest, an If-Then-Else statement generally checks a constant, property, or script for an expected value. If the constant is true, or the value of a property is returned, then a consequence occurs (such as the execution of the page shown above). In the case of the above example, if the property condition is not as expected, the Else action is provided to exit that portion of the test.
Add a Switch CloudTest supports Switch containers to control the flow of a test by the use of a property, constant, or script when working with unknown responses that fall within a known range, such as product options from a form, finite keys, or days of the week.