Creating Transactions
About Transactions
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. In a site that includes a shopping cart, a user logs into that site, adds an item to their cart, and checks out. Each of these steps can be thought of as a transaction—the performance of which can be measured as a transaction. 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. Once logically grouped, the Transaction provides a convenient means to measure the amount of time it takes a server to perform a given defined task or set of tasks. |
![]() |
For example, the Transaction shown above (in Icon view) contains a CloudTest page that equates to a Send Money Form page in a web application. By constructing the test as a Transaction, metrics about the specific “transaction” (e.g. submitting a form) can be captured. Among the metrics captured is the server response time it takes to submit all or part of a Transaction. An individual Transaction can be measured again at various increments of load. The resulting metrics are useful in identifying potential bottlenecks as an outcome of testing discrete business processes. The Transaction above is shown in List view below. A border surrounds the individual clip elements inside of the Transaction, Submit Send Money Form (shown right). | ![]() |
Creating Transactions in Icon View
The clip (shown right) was recorded from an ecommerce site. The test case includes discrete steps in a retail process to Add Items to Cart, Search Items, and to Purchase Items. The recording was converted with dynamic pages enabled. |
![]() |
|
![]() |
|
![]() |
|
![]() |
The Transaction is expanded when first created. | ![]() |
|
![]() |
|
![]() |
|
![]() |
|
![]() |
Creating Transactions in List View
|
![]() |
|
![]() |
|
![]() |
The Transaction is expanded when first created. | ![]() |
|
![]() |
|
![]() |
|
![]() |
|
![]() |
Transactions appear in the Result Details navigation tree just as other hierarchical relationships from the CloudTest repository. | ![]() |
The results example (above right) shows a clip recorded from an ecommerce site. In the example, a Transaction has been created for discrete steps in the fulfillment process, and each transaction has been renamed to make each step easier to identify in results. | ![]() |
When a Transaction contains one or more errors, it displays the error icon in the navigation tree by default. If error handling is not set to “fail the parent” then the error icon is not shown at the Transaction level. | ![]() |
Select a Transaction in either the left Navigation Tree or in the top Cover Flow to display its statistics in the Summary or Events Lists below. | ![]() |
Transactions in Basic Widgets
Collections, including Transactions, appear in all metrics that show collections together as a single measurable metric. Transactions appear for all widgets that display hierarchical relationships from the CloudTest repository, nested clips and nested collections now appear. Nesting is now reflected in the Clip Analysis, Clip Element Analysis, Collection Analysis, and Composition Analysis.Clip Element Analysis Transaction containers appear in the parent clip’s object hierarchy at the same level as other clip elements that reside at that level. |
![]() |
Collection Analysis
Transactions are shown in the Collection Analysis chart. Using this chart in combination with renamed transactions produces a clear outline of each step in a business process. |
![]() |
Composition Analysis
The Composition Analysis also shows the object hierarchy, including clip elements such as transactions. Uncheck Messages and Actions to narrow the display to Collections within a given Clip in this widget. |
![]() |