GermainUX integrates with Selenium to record, deploy, schedule, execute, monitor, and troubleshoot synthetic user scenarios.
Synthetic scenarios reproduce critical user workflows—such as login, search, checkout, or document access—so GermainUX can verify continuously that they remain available and functional.
🎁 Benefits
|
Capability |
Benefit |
|---|---|
|
Scenario Recording |
Record Selenium scenarios more easily with the GermainUX RPA Bot Recorder. |
|
Centralized Deployment |
Deploy and manage Selenium scripts across monitored environments. |
|
Remote Management |
Update, restart, control, and manage scenario versions remotely. |
|
Continuous Execution |
Run Selenium scenarios continuously through the GermainUX Engine. |
|
Manual or Scheduled Execution |
Run scenarios on demand or according to a recurring schedule. |
|
Monitoring and Replay |
Record and replay videos of scenario executions to determine which scenario failed, where it failed, and why. |
|
Independent Recording |
Record synthetic execution videos whether or not GermainUX Real User Monitoring is enabled in the target application. |
Video replay is especially useful when thousands of synthetic scenarios run across multiple applications and teams need to locate and diagnose a specific failure quickly.
💡 Common Use Cases
|
Use case |
Description |
|---|---|
|
Proactive issue detection |
Detect an application or workflow failure before it affects real users. |
|
Recurring health checks |
Confirm continuously that critical application features remain functional. |
|
Conversion monitoring |
Verify workflows such as product search, cart, checkout, and payment. |
|
Application availability |
Confirm that users can open an application, authenticate, and reach critical pages. |
|
Workflow validation |
Validate multi-step processes after a deployment or configuration change. |
|
Document and download testing |
Confirm that users can open or download documents such as PDFs. |
▶️ Run and Manage Scenarios
Go to:
GermainUX Workspace > Automation > Click
From this area, you can configure, execute, schedule, and monitor synthetic scenarios.
📋 Prerequisites
🌐 Supported Browsers
Synthetic scenarios can run with supported versions of:
|
Browser |
|---|
|
Chrome |
|
Edge |
|
Firefox |
|
Internet Explorer, where supported by the applicable GermainUX and Selenium versions |
Headless Chrome is recommended for scalable, unattended execution when a visible browser is not required.
⚙️ Browser and WebDriver Compatibility
The browser installed on the machine executing the scenario must be compatible with the WebDriver used by GermainUX.
An incompatible browser and driver combination can prevent the scenario from starting or cause interactions to fail unexpectedly. Validate compatibility whenever the browser or WebDriver is upgraded.
⚛️ Selenium and Selenide
Selenide is not required to create GermainUX synthetic scenarios. Selenium provides the underlying capabilities needed for:
|
Capability |
|---|
|
Explicit and conditional waiting |
|
WebDriver control |
|
Browser and element interactions |
|
AJAX-aware synchronization logic |
|
Screenshots |
|
Multiple tabs and windows |
|
Custom convenience methods |
Selenide can still be used when its higher-level syntax or additional abstractions are preferred.
🔍 Example: Validate a PDF Opened from Salesforce
A synthetic scenario can confirm that a user can open a PDF from Salesforce or another web application.
The scenario can be recorded with the GermainUX RPA Bot Recorder. If the document opens in another browser tab or window, use Selenium window handles to switch to the new context and validate the result.
See Selenium window-handle guidance.
The same approach can be used with other applications and workflows involving:
|
Workflow item |
|---|
|
New tabs or windows |
|
PDFs and downloadable documents |
|
External authentication pages |
|
Third-party payment pages |
|
Redirected workflows |
📄 Summary
GermainUX simplifies the complete lifecycle of Selenium scenarios:
Record → Deploy → Schedule → Execute → Monitor → Replay → Diagnose
Component: Engine
Feature Availability: 8.6.0 or later