Create / Edit Service Test - Web Transaction (Browser Simulation Mode - Step)

A Web transaction consists of a series of steps. Each step consists of one or more user actions. Use this page to create and edit a step.

Input Parameters

Parameter	Description
Name	Enter the name of the step.
Nonsensitive Parameters	The Recorder automatically extracts user specified values and populates them here. A user name is an example of a Nonsensitive Parameter and is not encrypted. Click the icon to add more Nonsensitive Parameters.
Sensitive Parameters	The Recorder automatically extracts user specified values and populates them here. A password is an example of a Sensitive Parameter and is encrypted before it is displayed. For example: If the Sensitive Parameter Name = PWD and Value = ******, PWD will be substituted with the real value in the URL or POST Data fields. Click the icon to add more Sensitive Parameters.

Parameter

Description

Name

Enter the name of the step.

Nonsensitive Parameters

The Recorder automatically extracts user specified values and populates them here. A user name is an example of a Nonsensitive Parameter and is not encrypted. Click the icon to add more Nonsensitive Parameters.

Sensitive Parameters

The Recorder automatically extracts user specified values and populates them here. A password is an example of a Sensitive Parameter and is encrypted before it is displayed.

For example: If the Sensitive Parameter Name = PWD and Value = ******, PWD will be substituted with the real value in the URL or POST Data fields.

Click the icon to add more Sensitive Parameters.

Actions

These actions are automatically recorded by the Recorder. If the Transaction Playback Mode is Browser Simulation, the following commands are available:

Commands	Description
Check	Checks a check box.
Click	Clicks an HTML element .
Close	Closes a browser window. This action is not captured by the Recorder and can be manually entered. For example: Choose Close in the dropdown box and type windowIndex="0" to Close the first window or type windowIndex="1" to Close the second window.
goBack	Simulates a click on the Browser Back button. This action is not captured by the Recorder and can be manually entered. For example: Choose goBack in the dropdown box and type windowIndex="0" to simulate goBack on the first window or type windowIndex="1" to simulate goBack on the second window.
keyDown	Simulates a key down event.
keyPress	Simulates a key press event.
keyUp	Simulates a key up event.
mouseDown	Simulates a mouse down event.
mouseMove	Simulates a mouse move event.
mouseUp	Simulates a mouse up event.
Open	Goes to a specified URL .
Refresh	Simulates a click on the Browser Refresh button. This action is not captured by the Recorder and can be manually entered. For example: Choose Refresh in the dropdown box and type windowIndex="0" to simulate a browser Refresh on the first window or type windowIndex="1" to simulate browser Refresh on the second window.
Select	Selects an entry in a drop down box.
Type	Enters text in a text input field or text area .
Uncheck	Unchecks a check box.
waitForPageToLoad	Waits for a specific page to load or timeouts within a specified number of milliseconds.
waitForPopUp	Waits for a specific popup window to close or timeouts within a specified number of milliseconds.
sleep	Sleeps for a specified number of milliseconds. This action is not captured by the Recorder and can be manually entered. For example: Choose sleep in the dropdown box and type timeout="3000" to simulate waiting for 3 seconds (300 milliseconds)

Validation

Parameter	Description
Success / Failure Strings	Success and Failure Strings are used to validate the content of the pages downloaded by the beacon. A Success / Failure String can be one of the following: Regular Text: The literal string is compared against the content of a page. Regular Expression: The string is treated as a regular expression that is matched against the content of a page. Each Success String must appear at least once within a transaction. Failure Strings should not appear within a step. If a Failure String appears within a transaction, or a Success String does not appear within a transaction, it is considered to be unsuccessful. Click the symbol to add more Success and Failure Strings. These strings are used in addition to the Success / Failure Strings specified for the transaction. Note: Only beacons that are 10.2.0.4 and above support Regular Expression mode.

Parameter

Description

Success / Failure Strings

Success and Failure Strings are used to validate the content of the pages downloaded by the beacon. A Success / Failure String can be one of the following:

Regular Text: The literal string is compared against the content of a page.
Regular Expression: The string is treated as a regular expression that is matched against the content of a page.

Each Success String must appear at least once within a transaction. Failure Strings should not appear within a step. If a Failure String appears within a transaction, or a Success String does not appear within a transaction, it is considered to be unsuccessful. Click the symbol to add more Success and Failure Strings. These strings are used in addition to the Success / Failure Strings specified for the transaction.

Note: Only beacons that are 10.2.0.4 and above support Regular Expression mode.

Related Topics

About Services

About Web Application Management

Enterprise Manager Information Roadmap