A page is a set of sequential requests sent from a single web page. A page object is created for each web page visited during the recording. Pages can be created automatically during recording but can be modified after recording by right-clicking and selecting Edit Page.
You can also create a new page after recording by:
1. Right-clicking on the top-level request, which does not already belong to a page, and then selecting Create Container > Create Page.
A transaction is a set of sequential requests representing a meaningful step in a test scenario. It tracks performance characteristics of time-critical business transactions consisting of several user actions. Transactions add another level of performance tracking in addition to requests and pages.
You can define transactions while recording a test case, as described in the Creating Transactions section, or after the test case is created.
To define a transaction after the test case is created:
1. Go to the Build Test Case node.
Transactions can also be nested. You can nest current transactions by:
1. Right-click on the top-level transaction you wish to be nested and select Create Container > Create Transaction.
Info: All page and transaction properties are displayed in the property grid. You can modify any property which is not grayed out.
The full list of properties, toolbar commands, and context menu options are provided in the User Interface Reference -> Test Case Tree -> Page.
Another way to create a page or transaction is to select multiple requests or objects in the test case tree -> right-click -> select Create Page or Create Container > Create Transaction. This will create a page or transaction around the selected objects.
Transaction and page properties
Some of the properties of transactions and pages are described in the following several sections. They share most properties so all mention of transaction objects will also apply to page objects unless otherwise stated.
The test run report will display transition metrics for every transaction. The metrics will be identified by the transaction's name. This is why it is encouraged to provide a meaningful name for every transaction.
In a test with multiple test cases, each test case may have multiple transactions, so the test report may be difficult to analyze. To make it easier, transactions in the same test case can be grouped by adding a prefix to their names.
To add a prefix to every transaction in a test case:
- No labels