Synthetic User Monitoring (SUM) Selenium capability gives the possibility for SUM to collect performance and availability metrics from the execution of a Selenium IDE script. On this page you find an overview on how this functionality works and in the following you find how to configure SUM with Selenium.
This gives the possibility to include the client rendering (in the Web browser) in the monitored performance. So this is closer to the experience faced by an end-user.
Selenium is an open source framework dedicated to Web application tests.
It is composed of several components.
In the context of the Synthetic User Monitoring Selenium capability, the involved Selenium components are mainly:
IMPORTANT: Selenium is not developed by SAP.
Usually designed with the Selenium IDE component, a Selenium IDE script (or SIDE file) corresponds to a Selenium IDE project.
It describes the sequences of actions (also referred to as commands) to be performed on a Web browser, such as clicks, setting texts, and waiting for elements.
These sequences are organized into:
Each action has a set of attributes to indicate:
Selenium IDE proposes several different commands, most of which are supported by Synthetic User Monitoring. (Refer to Which Selenium commands does SUM support)
To help with the script creation, the Selenium IDE proposes a recorder.
It also gives the possibility to play back the script.
When such a script is saved via the Selenium IDE, it generates a ".side" file.
This file is the JSON representation of the sequence of actions.
The SUM robot can be instructed to execute the SUM Selenium scenario locally or remotely.
This must be configured in the scenario configuration.
The SUM scenario is executed from the SUM location host.
In other words, it is executed via a webdriver and a Web browser located on the location host.
The local execution requires some specific configuration on the location host.
The scenario is executed from the indicated remote location.
In other words, it is executed via the webdriver pointed by the remote URL indicated in the scenario configuration.
The remote location can be one of the following: