Skip to content

Selenium Settings Dialog

Selenium Profiles

Rapise can playback web tests on Selenium nodes. Configure each Selenium node you need for testing in a separate profile using the Selenium Settings Dialog.

This dialog box displays the list of Selenium Profiles and allows you to create a new profile, modify an existing one, or create a new profile based on an existing one.

selenium_settings

How to Open

You can open this dialog box from the Rapise Settings > Selenium menu.

This dialog box has the following menu options:

  • Select Profile - This dropdown list allows you to select a different Selenium profile to display in the dialog.
  • Save - This button saves the changes to the current Selenium profile.
  • Test - This button tests the connection (URL) from Rapise to Selenium WebDriver (which connects to web browsers) and the connection from Selenium to the web browser.
  • Duplicate - This button creates a new Selenium profile based on the currently viewed one.
  • Create - This button creates a new empty Selenium profile that you can edit.
  • Rename - This button changes the name of the current Selenium profile being edited.
  • Delete - This button deletes the currently displayed Selenium profile. There is no undo, so exercise caution!

Local Selenium Profiles

Rapise version 6.3+ enables the creation of profiles local to a test. It allows storing profiles together with tests (inside a SpiraTest or Git repository) and eliminates the need to manually configure profiles on each execution host.

To create a local profile, simply press Duplicate for one of the global profiles and select the Local checkbox before clicking the OK button. Global and Local profiles may have the same name; in this case, the Local profile is used for execution.

Create Local Selenium Profile

If a test contains local Selenium profiles, they can be seen in the dropdowns.

Playback Profiles

Local Selenium profiles are stored inside the <Test Root>\Profiles\SeleniumProfiles folder.

Profile Options

Connection

This section allows you to enter the URI used to connect to the Selenium WebDriver server that hosts the web browsers being tested. It is typically in the form:

http://server:4444/wd/hub

Here, the port number used by Selenium is 4444 (default), and the /wd/hub suffix is added.

Important

If you are using web browsers on the local machine (the one running Rapise), you do not need to enter a URI and can leave the entire field blank.

Shared

This section contains common capabilities.

Browser Specific

In this section, set browser-specific options. Use the Chrome Specific section for configuring both Chrome and Edge browsers.

BrowserStack Settings

In addition, there are some settings unique to running Selenium WebDriver tests through the BrowserStack cloud platform:

selenium_settings_browserstack

  • BrowserStack
    • browserstack.key - This needs to be populated with your Browserstack cloud access key.
    • browserstack.user - This needs to be populated with your Browserstack username.
    • device - Specifies a particular mobile device for the test environment (mobile web only).
    • os_version - Use this capability to specify the OS version of the device.
    • realMobile - Use this flag to test mobile websites on a physical mobile device.

Parameterizing a Profile

Since Rapise 8.3, it is possible to use framework parameters in browser profiles. The syntax is:

{Parameter Name}

For example, a permanent browser profile path can be defined by a framework parameter and then used as:

["user-data-dir={UserDataDir}"]

Another example is setting the download folder location.

{"download.default_directory": "{DownloadFolder}"}

Note that the values of parameters may need to contain a double backslash as they must be valid escaped JavaScript strings.

UserDataDir=C:\\ProgramData\\Inflectra\\Rapise\\Temp\\Chrome
DownloadFolder=C:\\ProgramData\\Inflectra\\Rapise\\Temp\\Downloads

Profile with Parameters

See Also