EUEM Netprobe User Guide

Mozilla Firefox

Mozilla Firefox can be downloaded from http://www.mozilla.org/en-US/firefox/new/.

Installation is well-documented on the Mozilla website.

Selenium IDE

Selenium IDE is the primary tool for recording scenarios.

The Selenium IDE website is http://seleniumhq.org/projects/ide/. Selenium IDE can be downloaded via a link at the bottom right of the web page.

Installation is documented on the Selenium IDE website: http://seleniumhq.org/docs/02_selenium_ide.html#installing-the-ide

Scenario Script Format

Scenario scripts are saved in the NetProbe scenarios folder with an extension of *.geuem. Below is a simple example of a script that starts with a user performing a search for ITRS Group on google.com and navigating to the ITRS Group web site. It ends with the user clicking on the Products link.

    "url": "http://www.google.com.ph/",
	"scenario": "ITRS",
	"noofsteps": 5,
	"steps": [
	{
	"step": "open",
	"target": "/",
	"value": ""
	},
	{
	"step": "type",
	"target": "id=gbqfq",
	"value": "ITRS Group"
	},
	{
	"step": "click",
	"target": "id=gbqfb",
	"value": ""
	},
	{
	"step": "click",
	"target": "css=em",
	"value": ""
	},
	{
	"step": "clickAndWait",
	"target": "link=Products",
	"value": ""
	}
	]
	}

 

The fields on the scenario script are described below.

The header section contains the following fields.

Scenario View

This view shows details of a scenario, with its steps and elements. The Scenario View can be configured to show only steps.

Scenario Headline Legend

Script Editor

The Script Editor allows the user to configure a Geneos EUEM script. This script can be copied from Selenium IDE and pasted into the Script Editor. The script format is JSON.

Directory Structure

The EUEM folder is located in the plug-ins folder in the NetProbe installation.

The structure is as follows:

euem/
catalog/
sampler1/
_last/
gen/
runs/
<scenario1>/
<run1>/
<run2>/
<scenario2>/
scenarios/
sampler2/
…

Definitions

Actions

Actions are commands that generally manipulate the state of the application. They perform tasks that the user will carry out on a web page - for example, clicking a link or selecting an option. If an action fails, the execution of the current scenario is stopped.

Many actions have an "AndWait" suffix, for example, "clickAndWait". The "AndWait" suffix will cause the EUEM to make a call to the server and then wait for a new page to load.

Accessors

Accessors examine the state of the application and store the results in variables, e.g. "storeTitle". They are prefixed by "store" and are explicitly inserted by the user in a scenario script either by using the Selenium IDE or by manually manipulating the script itself. In EUEM, the variables are stored in the scenario run results file (JSON format).

Variables are found in a section of the .json file generated for each scenario run under the runs folder. For example:

"variables": {
"system": {
"url": "https://192.168.100.27/"
},
"user": {}
},
						
                        

There are two parts to the variables section. The first is "system", where EUEM stores system variables. The system variables include the following:

• Base URL
• Scenario Name
• Total steps
• Passed step count.

System variables can be accessed in the value field for other commands or by using echo() with syntax "${system.variable}".

The second is "user", where EUEM stores variables specified by the user in a scenario script.

User variables can be accessed in the value field for other commands or by using echo() with syntax "${variable}".

Assertions

Assertions verify that the state of the application conforms to what is expected. They are similar to accessors in that they examine the state of the application. There are three modes of assertions:

1. assert - commands with this prefix perform a hard assertion. This means that when an assert fails, the scenario is aborted.
2. verify - commands with this prefix perform a soft assertion. This means that when a verify fails, the scenario continues execution and logs the failure.
3. waitFor - commands with this prefix wait for some condition to become true. This is useful for AJAX applications. They will succeed immediately if the condition is already true. However, they will fail and halt the test if the condition does not become true within the current timeout setting.

Locator

An element locator tells EUEM which HTML element a command refers to - it is essentially an identifier. They are frequently used as attributes in Selenium commands. There are several ways of identifying a HTML element:

• Identifier/ID
• Name
• DOM
• Xpath
• CSS

This topic is discussed in the Selenium IDE documentation: http://seleniumhq.org/docs/02_selenium_ide.html

Behaviour

When using Selenium IDE to record scenario scripts, some Selenium commands are supported right out of the box. For example, if you click a button on a web page, Selenium IDE will record this as "click". Other commands are not directly supported.

The behaviour of each command is classified as follows:

• Automatically supported - the command is directly used by Selenium IDE. When interacting with a web page, Selenium IDE will use the command when appropriate.
• Explicit command - the command is not directly used by Selenium IDE. To use an explicit command, you will need to insert the command in the scenario script - either by using Selenium IDE or by hand.
• Alternate command - this is a command that can be used explicitly in place of the automatically supported command. For example, when checking a checkbox on a web page, Selenium IDE records this activity as a "click". Instead of click, you can replace this command with a "check" by using Selenium IDE or by hand.

Text Patterns

Many commands, particularly assertions, use text patterns as parameters. For example, assertText(locator, pattern). Pattern refers to the text pattern for the command to compare against.

EUEM supports an exact text match for use with these commands. This means that the text seen by the user on the web page is checked against the exact text entered for the command in the scenario. Whitespaces before and after text and special characters such as carriage returns, are removed prior to comparison.

Actions

This section lists the actions supported by EUEM.

This command adds a selection to the set of selected options in a multi-select element using an option locator.

Scenario Table Legend

Menu Options

EUEM has an additional context-menu option for viewing error messages when a scenario doesn't run correctly.

Show Scenario Detailed Log

This command allows you to view a detailed log of a scenario error. It can be accessed by a right-click on the samplingStatus field and selecting "Show Scenario Detailed Log" from the context menu.

Clicking the menu item will pop up an Output box that either gives a stack trace or more description on the error.

Plug-in Configuration

The EUEM plug-in can be configured in two steps:

1. Record scenario scripts using the Selenium IDE with the Geneos EUEM plug-in installed.
2. Upload the scenario scripts into the Gateway Setup Editor (GSE) and configure the parameters for playback of the scripts.

This section describes the second step and subsequent sections describe the first step. There are basically two levels of configuration in the Gateway Setup Editor for EUEM:

1. Scenario level configuration. The first set of configuration is for individual scenarios. For example, timeouts can be configured for a scenario, overriding the settings on the sampler level configuration.
2. Sampler level configuration. This level of configuration applies to all scenarios in the sampler.

Scenario Level Configuration

Located on the Basic tab of the EUEM plug-in configuration in the Gateway Setup Editor, the following parameters can be configured for individual scenarios:

Sampler Level Configuration

Located on the Advanced tab of the EUEM plug-in configuration in the Gateway Setup Editor, the following parameters can be configured for a EUEM sampler:

Prerequisites for Recording Scenarios

There are three components that need to be installed in order to record scenario scripts for EUEM:

1. Mozilla Firefox
2. Selenium IDE
3. Geneos EUEM Firefox Plug-in

EUEM has been verified to work with Firefox version 14.0.1 and Selenium IDE version 1.8.1 up to 1.9.0.

Geneos EUEM Firefox Plug-in

Follow these steps to install the Geneos EUEM Firefox plug-in:

1. Open Mozilla Firefox.
2. On the toolbar, select Tools > Add-ons. This will open the Add-ons Manager in a tab on the browser.
3. Click the "Tools for all add-ons" button and select "Install Add-on From File".

4. On the dialog box, navigate to the Geneos EUEM Firefox plug-in file (itrs-geneos-euem.xpi) and press Open. The EUEM Firefox plug-in should show up on the Firefox Add-ons list.

Recording Scenario Scripts

Recording with Selenium IDE

To record a scenario script, follow these steps:

1. On Mozilla Firefox, click Tools from the toolbar and select Selenium IDE. This will open Selenium IDE in a separate window, which by default will be in recording mode. You can verify this by holding the mouse pointer over the red record button on the upper right.
2. On Firefox, navigate to the web page to be monitored and carry out the actions. Selenium IDE will record your actions as commands on the scenario script.
3. When the scenario is completed, click the record button to stop Selenium IDE from recording.
4. To save the scenario script, click File on the toolbar, select "Export Test Case As" and then select "Geneos EUEM Format" to save the script as a EUEM JSON file (*.geuem).

Inserting Explicit Commands

Not all commands are automatically recorded by Selenium IDE. Commands such as assertions and accessors are inserted manually by the user, either by using Selenium IDE or by using a plain text editor for the scenario script itself.

To insert an explicit command:

1. Right-click on the script in Selenium IDE.
2. Select "Insert New Command" from the context menu.

3. Select the command to insert using the Command dropdown or simply type it in. In the example below, assertText is inserted.
4. The assertText command requires a parameter - a text pattern to assert against. On the Target text field, enter the text pattern to be used in the assertion. In this example, "Dashboard" is entered. This means that the scenario will assert the presence of "Dashboard" text on the web page.

Using the Geneos EUEM Firefox Plug-in

When the Geneos EUEM Firefox Plug-in is installed in Firefox, a toolbar will appear in Selenium IDE:

The toolbar gives access to custom commands that will assist in recording scenario scripts for EUEM.

    "url": "http://www.google.com.ph/",
	"scenario": "ITRS",
	"noofsteps": 5,
	"steps": [
	{
	"step": "open",
	"target": "/",
	"value": ""
	},
	{
	"step": "type",
	"target": "id=gbqfq",
	"value": "ITRS Group"
	},
	{
	"step": "click",
	"target": "id=gbqfb",
	"value": ""
	},
	{
	"step": "click",
	"target": "css=em",
	"value": ""
	},
	{
	"step": "clickAndWait",
	"target": "link=Products",
	"value": ""
	}
	]
	}
							
                            

Historical Result Files

The EUEM plug-in stores generated files and results of playback runs on the NetProbe directory.

euem/
catalog/
sampler1/
_last/
gen/
runs/
<scenario1>/
<run1>/
<run2>/
<scenario2>/
scenarios/
sampler2/
…

Files and Folders

The following folders and files are found in the EUEM directory.

_last/Folder

This folder contains csv files with the latest run results for each scenario.

The following files are stored in this folder:

gen/ Folder

This folder contains generated executable JavaScript (*.js) files that can be run by PhantomJS.

Scenario Run Folders

There is a sub-folder for each configured scenario under the runs/ folder. These folders are named based on their scenario names.

Under each scenario folder is a sub-folder for each playback run. The naming convention used for these folders is YYYY_MM_DDTHH_MM_SSZ, based on the start date and time of the execution of the script.

Several files are stored in this folder:

scenarios/ Folder

This folder contains the scenario scripts for the NetProbe.

Selenium Commands

There are three types of Selenium commands available in Selenium IDE: Actions, Accessors and Assertions. Each type of command is described below. There are over 500 Selenium commands, but only a subset, useful for monitoring, is supported by the Geneos EUEM plug-in.

Each command call has three elements:

1. Command - the specific Selenium command, which can be an action, accessor or an assertion.
2. Target - the page element on which the command will be performed. By convention, this is also the first parameter in a command. In Selenium, an element locator is a means of telling the command which page element is being referred to; it is an identifier.
3. Value - the value of the user input. By convention, this is the second parameter in a command. For example, when using the type() command, the value is the text typed by the user.

This section defines key terms to understand Selenium commands and lists the actions, accessors and assertions that are supported by EUEM.

"variables": {
"system": {
"url": "https://192.168.100.27/"
},
"user": {}
},
							
                            

Assertions

This section lists assertions supported by EUEM.

assertAlert(pattern)

This command retrieves the message of a JavaScript alert generated during the previous action, or fails if there were no alerts.

Getting an alert has the same effect as manually clicking OK. If an alert is generated but you do not consume, the next action will fail.

JavaScript alerts that are generated in a page's onload() event handler are not supported.

Arguments are:

Behaviour: Explicit command.

assertAlertNotPresent()

This command returns true if there is no JavaScript alert present, otherwise false.

There are no arguments for this command.

Behaviour: Explicit command.

assertAlertPresent()

This command returns true if there is a JavaScript alert present, otherwise false.

There are no arguments for this command.

Behaviour: Explicit command.

assertBodyText(pattern)

This command compares the text of a web page to a given text pattern. Since HTML body text can be quite long, this command is useful only for small web pages.

Arguments are:

Behaviour: Explicit command.

assertChecked(locator)

Asserts whether a toggle-button (checkbox/radio button) is checked. Returns true if the checkbox is checked, otherwise false. Fails if the specified element doesn't exist or isn't a toggle-button.

Arguments are:

Behaviour: Explicit command.

assertElementPresent(locator)

This command asserts that the specified element is present somewhere on the web page. Returns true if the element is present, otherwise false.

Arguments are:

Behaviour: Explicit command.

assertLocation(pattern)

Obtains the absolute URL of the current page and compares it against the pattern supplied by the user.

Arguments are:

Behaviour: Explicit command.

assertSelectedId(locator, pattern)

This command asserts the id of a selected option of a dropdown.

For example:

<option id="de" value="dep">Deposit</option>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

assertSelectedIds(locator, pattern)

This command gets an array of all the selected ids from a multi-select dropdown and asserts this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

assertSelectedIndex(locator, pattern)

This command asserts the index of a selected option of a dropdown.

In this example, the Deposit option has an index of 0.

<select>
<option id="de" value="dep">Deposit</option>
							<option id="wi" value="wit">Withdraw</option>
							</select>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

assertSelectedIndexes(locator, pattern)

This command gets an array of all the selected indexes from a multi-select dropdown and asserts this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

assertSelectedLabel(locator, pattern)

This command asserts the label of a selected option of a dropdown.

In this HTML snippet, "Deposit" is the label:

<option value="dep">Deposit</option>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

assertSelectedLabels(locator, pattern)

This command gets an array of all the selected labels from a multi-select dropdown and asserts this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

assertSelectedValue(locator, pattern)

This command asserts the value of a selected option of a dropdown.

For example:

<option value="dep">Deposit</option>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

assertSelectedValues(locator, pattern)

This command gets an array of all the selected values from a multi-select dropdown and asserts this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

assertText(locator, pattern)

This command compares the text of an element to a given text pattern.

Arguments are:

Behaviour: Explicit command.

assertTextNotPresent(pattern)

This command asserts that the specified text pattern does not appear somewhere on the rendered page shown to the user. Returns true if the pattern does not match the text, otherwise false.

Arguments are:

Behaviour: Explicit command.

assertTextPresent(pattern)

This command asserts that the specified text pattern appears somewhere on the rendered page shown to the user. Returns true if the pattern matches the text, otherwise false.

Arguments are:

Behaviour: Explicit command.

assertTitle(pattern)

This command gets the title of the current web page and compares it against the pattern supplied by the user.

Arguments are:

Behaviour: Explicit command.

assertValue(locator, pattern)

This command compares the value of an element with the supplied pattern.

Arguments are:

Behaviour: Explicit command.

assertVisible(locator)

This command checks the visibility of an element. Returns true if the element is visible, otherwise false. This command fails if the element is not present.

An element can be rendered not visible by setting the CSS "visibility" property to "hidden", or the "display" property to "none".

Arguments are:

Behaviour: Explicit command.

verifyElementPresent(locator)

This command verifies that the specified element is somewhere on the page. Returns true if the element is present, otherwise false.

Arguments are:

Behaviour: Explicit command.

verifyEval(script, pattern)

This command retrieves the result of the evaluating JavaScript snippet. The snippet may have multiple lines, but only the result of the last line will be returned.

Arguments are:

Behaviour: Explicit command.

verifyExpression(expression, pattern)

This command returns the result of the specified expression.

Arguments are:

Behaviour: Explicit command.

verifyNotTitle(pattern)

This command gets the title of the current web page and compares it with the pattern. Returns true if the title and pattern are not the same, false if they are the same.

Arguments are:

Behaviour: Explicit command.

verifySelectedId(locator, pattern)

This command verifies the id of a selected option of a dropdown.

For example:

<option id="de" value="dep">Deposit</option>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

verifySelectedIds(locator, pattern)

This command gets an array of all the selected ids from a multi-select dropdown and verifies this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

verifySelectedIndex(locator, pattern)

This command verifies the index of a selected option of a dropdown.

In this example, the Deposit option has an index of 0.

<select>
<option id="de" value="dep">Deposit</option>
							<option id="wi" value="wit">Withdraw</option>
							</select>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

verifySelectedIndexes(locator, pattern)

This command gets an array of all the selected indexes from a multi-select dropdown and verifies this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

verifySelectedLabel(locator, pattern)

This command verifies the label of a selected option of a dropdown.

In this HTML snippet, "Deposit" is the label:

<option value="dep">Deposit</option>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

verifySelectedLabels(locator, pattern)

This command gets an array of all the selected labels from a multi-select dropdown and verifies this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

verifySelectedValue(locator, pattern)

This command verifies the value of a selected option of a dropdown.

For example:

<option value="dep">Deposit</option>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

verifySelectedValues(locator, pattern)

This command gets an array of all the selected values from a multi-select dropdown and verifies this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

verifyText(locator, pattern)

This command gets the text of an element and compares it against a pattern. This works for any element that contains text. This command uses the rendered text shown to the user.

Arguments are:

Behaviour: Explicit command.

verifyTextNotPresent(pattern)

This command verifies that the specified text pattern does not appear somewhere on the rendered page shown to the user. Returns true if the pattern does not match the text, otherwise false.

Arguments are:

Behaviour: Explicit command.

verifyTextPresent(pattern)

This command verifies that the specified text pattern appears somewhere on the rendered page shown to the user. Returns true if the pattern matches the text, otherwise false.

Arguments are:

Behaviour: Explicit command.

verifyTitle(pattern)

This command gets the title of the current page and compares it against a pattern. This command refers to the text in the HTML title tag, for example <TITLE>Title text</TITLE>.

Arguments are:

Behaviour: Explicit command.

verifyValue(locator, pattern)

This command gets the (whitespace-trimmed) value of an input field (or anything else with a value parameter) and compares it against a pattern. For checkbox/radio elements, the value will be "on" or "off" depending on whether the element is checked or not. This command returns the element value, or "on/off" for checkbox/radio elements.

Arguments are:

Behaviour: Explicit command.

verifyVisible(locator)

This command determines if the specified element is visible. An element can be rendered invisible by setting the CSS "visibility" property to "hidden", or the "display" property to "none", either for the element itself or one of its ancestors. This method will fail if the element is not present.

Arguments are:

Assertions

This section lists assertions supported by EUEM.

assertAlert(pattern)

This command retrieves the message of a JavaScript alert generated during the previous action, or fails if there were no alerts.

Getting an alert has the same effect as manually clicking OK. If an alert is generated but you do not consume, the next action will fail.

JavaScript alerts that are generated in a page's onload() event handler are not supported.

Arguments are:

Behaviour: Explicit command.

assertAlertNotPresent()

This command returns true if there is no JavaScript alert present, otherwise false.

There are no arguments for this command.

Behaviour: Explicit command.

assertAlertPresent()

This command returns true if there is a JavaScript alert present, otherwise false.

There are no arguments for this command.

Behaviour: Explicit command.

assertBodyText(pattern)

This command compares the text of a web page to a given text pattern. Since HTML body text can be quite long, this command is useful only for small web pages.

Arguments are:

Behaviour: Explicit command.

assertChecked(locator)

Asserts whether a toggle-button (checkbox/radio button) is checked. Returns true if the checkbox is checked, otherwise false. Fails if the specified element doesn't exist or isn't a toggle-button.

Arguments are:

Behaviour: Explicit command.

assertElementPresent(locator)

This command asserts that the specified element is present somewhere on the web page. Returns true if the element is present, otherwise false.

Arguments are:

Behaviour: Explicit command.

assertLocation(pattern)

Obtains the absolute URL of the current page and compares it against the pattern supplied by the user.

Arguments are:

Behaviour: Explicit command.

assertSelectedId(locator, pattern)

This command asserts the id of a selected option of a dropdown.

For example:

<option id="de" value="dep">Deposit</option>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

assertSelectedIds(locator, pattern)

This command gets an array of all the selected ids from a multi-select dropdown and asserts this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

assertSelectedIndex(locator, pattern)

This command asserts the index of a selected option of a dropdown.

In this example, the Deposit option has an index of 0.

<select>
<option id="de" value="dep">Deposit</option>
							<option id="wi" value="wit">Withdraw</option>
							</select>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

assertSelectedIndexes(locator, pattern)

This command gets an array of all the selected indexes from a multi-select dropdown and asserts this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

assertSelectedLabel(locator, pattern)

This command asserts the label of a selected option of a dropdown.

In this HTML snippet, "Deposit" is the label:

<option value="dep">Deposit</option>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

assertSelectedLabels(locator, pattern)

This command gets an array of all the selected labels from a multi-select dropdown and asserts this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

assertSelectedValue(locator, pattern)

This command asserts the value of a selected option of a dropdown.

For example:

<option value="dep">Deposit</option>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

assertSelectedValues(locator, pattern)

This command gets an array of all the selected values from a multi-select dropdown and asserts this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

assertText(locator, pattern)

This command compares the text of an element to a given text pattern.

Arguments are:

Behaviour: Explicit command.

assertTextNotPresent(pattern)

This command asserts that the specified text pattern does not appear somewhere on the rendered page shown to the user. Returns true if the pattern does not match the text, otherwise false.

Arguments are:

Behaviour: Explicit command.

assertTextPresent(pattern)

This command asserts that the specified text pattern appears somewhere on the rendered page shown to the user. Returns true if the pattern matches the text, otherwise false.

Arguments are:

Behaviour: Explicit command.

assertTitle(pattern)

This command gets the title of the current web page and compares it against the pattern supplied by the user.

Arguments are:

Behaviour: Explicit command.

assertValue(locator, pattern)

This command compares the value of an element with the supplied pattern.

Arguments are:

Behaviour: Explicit command.

assertVisible(locator)

This command checks the visibility of an element. Returns true if the element is visible, otherwise false. This command fails if the element is not present.

An element can be rendered not visible by setting the CSS "visibility" property to "hidden", or the "display" property to "none".

Arguments are:

Behaviour: Explicit command.

verifyElementPresent(locator)

This command verifies that the specified element is somewhere on the page. Returns true if the element is present, otherwise false.

Arguments are:

Behaviour: Explicit command.

verifyEval(script, pattern)

This command retrieves the result of the evaluating JavaScript snippet. The snippet may have multiple lines, but only the result of the last line will be returned.

Arguments are:

Behaviour: Explicit command.

verifyExpression(expression, pattern)

This command returns the result of the specified expression.

Arguments are:

Behaviour: Explicit command.

verifyNotTitle(pattern)

This command gets the title of the current web page and compares it with the pattern. Returns true if the title and pattern are not the same, false if they are the same.

Arguments are:

Behaviour: Explicit command.

verifySelectedId(locator, pattern)

This command verifies the id of a selected option of a dropdown.

For example:

<option id="de" value="dep">Deposit</option>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

verifySelectedIds(locator, pattern)

This command gets an array of all the selected ids from a multi-select dropdown and verifies this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

verifySelectedIndex(locator, pattern)

This command verifies the index of a selected option of a dropdown.

In this example, the Deposit option has an index of 0.

<select>
<option id="de" value="dep">Deposit</option>
							<option id="wi" value="wit">Withdraw</option>
							</select>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

verifySelectedIndexes(locator, pattern)

This command gets an array of all the selected indexes from a multi-select dropdown and verifies this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

verifySelectedLabel(locator, pattern)

This command verifies the label of a selected option of a dropdown.

In this HTML snippet, "Deposit" is the label:

<option value="dep">Deposit</option>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

verifySelectedLabels(locator, pattern)

This command gets an array of all the selected labels from a multi-select dropdown and verifies this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

verifySelectedValue(locator, pattern)

This command verifies the value of a selected option of a dropdown.

For example:

<option value="dep">Deposit</option>

This command will fail when used on a dropdown with multiple selection enabled.

Arguments are:

Behaviour: Explicit command.

verifySelectedValues(locator, pattern)

This command gets an array of all the selected values from a multi-select dropdown and verifies this against a comma delimited text pattern.

Arguments are:

Behaviour: Explicit command.

verifyText(locator, pattern)

This command gets the text of an element and compares it against a pattern. This works for any element that contains text. This command uses the rendered text shown to the user.

Arguments are:

Behaviour: Explicit command.

verifyTextNotPresent(pattern)

This command verifies that the specified text pattern does not appear somewhere on the rendered page shown to the user. Returns true if the pattern does not match the text, otherwise false.

Arguments are:

Behaviour: Explicit command.

verifyTextPresent(pattern)

This command verifies that the specified text pattern appears somewhere on the rendered page shown to the user. Returns true if the pattern matches the text, otherwise false.

Arguments are:

Behaviour: Explicit command.

verifyTitle(pattern)

This command gets the title of the current page and compares it against a pattern. This command refers to the text in the HTML title tag, for example <TITLE>Title text</TITLE>.

Arguments are:

Behaviour: Explicit command.

verifyValue(locator, pattern)

This command gets the (whitespace-trimmed) value of an input field (or anything else with a value parameter) and compares it against a pattern. For checkbox/radio elements, the value will be "on" or "off" depending on whether the element is checked or not. This command returns the element value, or "on/off" for checkbox/radio elements.

Arguments are:

Behaviour: Explicit command.

verifyVisible(locator)

This command determines if the specified element is visible. An element can be rendered invisible by setting the CSS "visibility" property to "hidden", or the "display" property to "none", either for the element itself or one of its ancestors. This method will fail if the element is not present.

Arguments are:

Behaviour: Explicit command.

waitForBodyText(pattern)

This command waits for the entire text of the page to evaluate to true against the supplied pattern before continuing.

Arguments are:

Behaviour: Explicit command.

waitForChecked(locator)

This command gets whether a toggle-button (checkbox/radio) is checked. It fails if a specified element doesn't exist or isn't a toggle-button. Returns true if the checkbox is checked, otherwise false.

Arguments are:

Behaviour: Explicit command.

waitForCondition(script, timeout)

This command runs the specified JavaScript snippet repeatedly until it evaluates to true. The snippet may have multiple lines, but only the result of the last line is considered.

Arguments are:

Behaviour: Explicit command.

waitForElementPresent(locator)

This command verifies that the specified element is somewhere on the page. Returns true if the element is present, otherwise false.

Arguments are:

Behaviour: Explicit command.

waitForEval(script, pattern)

This command obtains the result of evaluating the specified JavaScript snippet. The snippet may have multiple lines but only the result of the last line will be returned.

Arguments are:

Behaviour: Explicit command.

waitForPageToLoad(timeout)

This command pauses the execution of the scenario script until an expected new page loads.

Arguments are:

Behaviour: Explicit command.

waitForText(locator, pattern)

This command gets the text of an element and compares it against a pattern. This works for any element that contains text. This command uses the rendered text shown to the user.

Arguments are:

Behaviour: Explicit command.

waitForTextNotPresent(pattern)

This command verifies that the specified text pattern does not appear somewhere on the rendered page shown to the user. Returns true if the pattern matches the text, otherwise false.

Arguments are:

Behaviour: Explicit command.

waitForTitle(pattern)

This command gets the title of the current page - i.e. the text between <TITLE> and </TITLE> tags and compares it with a text pattern.

Arguments are:

Behaviour: Explicit command.

waitForValue(locator, pattern)

This command obtains the (whitespaced-trimmed) value of an input field (or anything else with a value parameter). For checkbox/radio elements, the value will be "on" or "off" depending on whether the element is checked or not. The command returns the element value, or "on/off" for checkbox/radio elements.

Arguments are:

Behaviour: Explicit command.

waitForVisible(locator)

This command determines if the specified element is visible. An element can be rendered invisible by setting the CSS "visibility" property to "hidden", or the "display" property to "none", either for the element itself or one of its ancestors. This method will fail if the element is not present. Returns true if the specified element is visible, false otherwise.

Arguments are:

Behaviour: Explicit command.

Custom Commands

The EUEM plug-in includes additional commands that are outside the standard set included with Selenium IDE. Custom commands, not being part of the standard set of Selenium commands, have a couple of limitations:

1. Custom commands do not show up in the Selenium IDE commands dropdown.
2. Custom commands do not have a reference (i.e. context sensitive documentation) when they are used in Selenium IDE.

Due to the first limitation, the Geneos EUEM Firefox plug-in has buttons for the user to insert these commands.

downloadFile(urlLocation, filename)

This command downloads a file from a given URL. The download file must follow the rules on cross domain file scripting which means this command cannot be used if the base URL for the scenario is different from the file.

Arguments are:

Behaviour: Explicit command - can be called by pressing the Geneos EUEM Firefox plug-in button ().

loginWithBasicAuthentication(url, authenticationDetails)

This command opens a URL with basic authentication.

Use this command when authentication details are needed to enter a site and the straight recording from Selenium IDE (which will record a login as type() and click()) doesn't work.

Arguments are:

Behaviour: Explicit command - can be called by pressing the Geneos EUEM Firefox plug-in button ().

setViewport(width, height)

This command sets the page viewport of the browser's window. This will determine the dimensions of the screenshot when catpureEntirePageScreenshot() is used.

Arguments are:

Behaviour: Explicit command - can be called by pressing the Geneos EUEM Firefox plug-in button ().

storeAsMHT(url, filename)

This command saves the current web page as a MIME HTML (*.mht), a web page archive format. This is saved in the scenario run folder on the Netprobe.

Arguments are:

Behaviour: Explicit command - can be called by pressing the Geneos EUEM Firefox plug-in button ().

Unsupported Commands

Not all commands available in Selenium IDE are supported by the EUEM plug-in. Selenium IDE will not prevent the user from using an unsupported command.

EUEM will warn you about the use of unsupported commands in two ways:

1. A warning popup on using the Copy to Clipboard button.

2. A comment on the Geneos EUEM JSON script. For example:

{
"comment": "*** UNSUPPORTED COMMAND ***",
							"step": "allowNativeXpath",
							"target": "",
							"value": ""
							},
						
                        

Unsupported commands will show up as a failed step when the scenario is run, but does not stop the scenario run.

Unsupported Commands

Not all commands available in Selenium IDE are supported by the EUEM plug-in. Selenium IDE will not prevent the user from using an unsupported command.

EUEM will warn you about the use of unsupported commands in two ways:

1. A warning popup on using the Copy to Clipboard button.

2. A comment on the Geneos EUEM JSON script. For example:

{
"comment": "*** UNSUPPORTED COMMAND ***",
							"step": "allowNativeXpath",
							"target": "",
							"value": ""
							},
						
                        

Unsupported commands will show up as a failed step when the scenario is run, but does not stop the scenario run.