This dialog box displays the list of mobile devices that have been configured for use by Rapise and lets you create a new profile, modify a profile or make a new profile based on an existing one.
How to Open
You can open this dialog box from the Rapise Options ribbon, it is the Selenium Settings button in the Web Testing tab.
This dialog box has the following menu options:
·Select Profile - This dropdown list lets you select a different Selenium profile to be displayed in the dialog.
·Save - This button will save the changes to the current Selenium profile.
·Test - This button will test the Connection (URL) from Rapise to Selenium WebDriver (which is used to connect to the web browsers) and the connection from Selenium to the web browser.
·Duplicate - This button will create a new Selenium profile based on the currently viewed one.
·Create - This button will create a new empty Selenium profile that you can edit.
·Rename - This button will change the name of the current Selenium profile being edited.
·Delete - This button will delete the currently displayed Selenium profile. There is no undo, so be careful!
This section lets you enter the URI used to connect to the Selenium WebDriver server which hosts the web browsers being tested. It is typically of the form:
Where the port number used by Selenium is 4444 by default and the /wd/hub suffix is added.
If you are using web browsers on the local machine (that is running Rapise) you don't need to enter in a URI and can leave the entire field blank.
This section has various settings, some of which are used by all web browsers, some are browser specific:
obrowserName - The name of the browser being automated. The current allowed values are:
oplatform - A key specifying which platform the browser should be running on. This is used by Selenium Grid and/or cloud platforms such as SauceLabs to dynamically select the appropriate Selenium server. For other cases you can leave blank. The allowed values for Selenium Grid include:
oversion - The browser version to use. This is used by Selenium Grid and/or cloud platforms such as SauceLabs to dynamically select the appropriate Selenium server. For other cases you can leave blank.
odatabaseEnabled - Whether the session can interact with database storage.
olocationContextEnabled - Whether the session can set and query the browser's location context.
oapplicationCacheEnabled - Whether the session can interact with the application cache.
obrowserConnectionEnabled - Whether the session can query for the browser's connectivity and disable it if desired.
owebStorageEnabled - Whether the session supports interactions with storage objects.
oacceptSslCerts - Whether the session should accept all SSL certs by default.
orotatable - Whether the session can rotate the current page's current layout between portrait and landscape orientations (only applies to mobile platforms).
onativeEvents - Whether the session is capable of generating native events when simulating user input.
ounexpectedAlertBehaviour - What the browser should do with an unhandled alert before throwing out the UnhandledAlertException. Possible values are 'accept', 'dismiss' and 'ignore'.
oelementScrollBehavior - Allows the user to specify whether elements are scrolled into the viewport for interaction to align with the top (0) or bottom (1) of the viewport. The default value is to align with the top of the viewport. Supported in IE and Firefox (since 2.36).
·Chrome Specific - this contains various settings specific to the Chrome web browser
·Firefox Specific -this contains various settings specific to the Firefox web browser
·IE Specific - this contains various settings specific to the IE web browser
·Safari Specific - this contains various settings specific to the Safari web browser
·Proxy - this contains various settings for using HTTP proxy servers when connecting from Rapise to Selenium WebDriver
·Remote WebDriver Specific
owebdriver.remote.quietExceptions - Disable automatic screnshot capture on exceptions. This is False by default.
Browser Stack Settings
In addition, there are some settings, unique to running Selenium WebDriver tests through the BrowserStack cloud platform:
obrowserstack.key - This needs to be populated with your Browserstack cloud access key
obrowserstack.user - This needs to be populated with your Browserstack username
odevice - Specifies a particular mobile device for the test environment (mobile web only).
oos_version - Use this capability to specify the OS version of the device.
orealMobile - Use this flag to test mobile websites on a physical mobile device.