HTTP page details

Page detail fields apply to the page that is currently selected.
General tab
Page title
Specifies the display name for the page. If the primary request returned a title, the display name for the page is the content between the <title></title> tags. If the primary request returned no title or an empty title, a name for the page is constructed from the first node in the web address for the primary request URL, for example, www.site.com/displayname/.... If two pages have the same page title but are at different web addresses (for their primary request), then a number might be appended to indicate that they are different (for example, displayname {1}, displayname {2}). The pages are included in reports as separate pages, with their unique appended names.
Pages with the same title and web address appear in the test editor with the same page title and in reports as the same page. Rename any pages that you want to be reported on under a different name. Renaming a page neither changes the value (if any) between the <title></title> tags nor affects how the test runs.
Primary request
Displays a hyperlink to the primary request for the page. This request is highlighted and is the request from which the display name for the page is derived.
Think time
Specifies the programmatically calculated time delay that is observed for each user when this test is run with multiple virtual users. Think time is a statistical emulation of the amount of time actual users spend reading or thinking about a page before requesting another page from the server.
Test data
Summarizes data substitutions and potential matches in the page. Right-click a row, or select a row and then click Options, to perform common operations. Double-click a row to navigate to the location where a substitution or potential match occurs. To associate a datapool candidate with a datapool, click the row, and then click Substitute. To remove a datapool substitution, click the row, and then click Remove Substitution. To find more locations in the test that have the same value as the selected row, click Find More. Click the icons to the left of the preview area to switch between an inline view and a hierarchical view of the selected data.
URL Encode
Indicates whether a test value contains special characters such as spaces or commas. With this option, special characters are encoded when variable data is substituted from a datapool.
Page title verification point
Indicates whether the page title verification point is enabled for this page. If so, Enable verification point is selected.
When Enable verification point is selected, the value between the <title></title> tags, if any, is copied to the Expected page title field on the properties page of the verification point. Click Edit Properties to change the Expected page title. The value between the title tags is different from the display page title (the value in the Page title field) that is used for reporting. Changing the Page title does not change the value between the title tags, and therefore does not affect what is initially copied to the Expected page title field.
If Enable verification point is selected, the test verifies whether the page returns the value in the Expected page title field. An error is reported in the test log if the title returned by the primary request for the page does not contain the expected title. Although the comparison is case-sensitive, it ignores multiple white-space characters (such as spaces, tabs, and carriage returns).
Enable response time breakdown
Enables collection of response time breakdown data. With response time breakdown, you can see statistics on any page element. The statistics show how much time was spent in each part of the system under test. You can use response time breakdown to identify code problems. You can see which application on which server is the performance bottleneck, and then drill down further to determine exactly which package, class, or method is causing the problem.

This option is displayed in multiple test elements. Enabling this option in an element also enables it in the element’s children. For example, enabling monitoring at the test level also enables monitoring at the page and request levels. You can enable monitoring for a specific page; doing so enables monitoring for the requests of that page, but not for other pages or their requests.

HTTP and SOA support response time breakdown. Other protocols do not support response time breakdown.

Advanced tab
Enable Requirements
Select to enable the use of performance and functional requirements for this test.
Name
Specifies the name of this set of enabled requirements. By default, it is the URL of the page. Although you can change the name to improve readability, only the Requirements report uses the changed name. Other reports use the default name. Click Use Defaults to reset Name to the default value.
Requirement
All performance and functional requirements are displayed in the table. Shaded requirements indicate that they are undefined. To define a requirement, set an Operator and Value. To apply the defined requirement to multiple pages, select the pages in the test, right-click the requirement row in the table, and click Copy Requirements.
Operator
Click this field to display a list of mathematical operators. Select an operator for this requirement.
Value
Click this field to set a numeric time value in milliseconds.
Standard
Select to enable this requirement to be processed by the report as a standard requirement. Standard requirements can cause a test to fail. Requirements that are not listed as standard do not cause the test to fail.
Hide Undefined Requirements
Select to prevent undefined requirements from appearing in the table. This hides the shaded rows.
Clear
Select one or more requirements and click to remove the definition. The requirement is still available and can be redefined.
Error Handling
Click to open the error condition table. You can use error handling to specify an action to take and a message to log when a specific condition occurs. Conditions include verification point failures, server timeouts, custom code alerts, and data correlation problems. All conditions are displayed in the table, along with the action to take and the message to log when the error occurs. To define an error handler, select a Condition, and then click Edit.
Hide unselected conditions
Click to display only the selected error handlers. Hiding a condition does not deactivate the condition.
Feedback