Product Dashboard
The Product Dashboard is the central monitoring hub for your RobusTest platform. It provides real-time and historical visibility into device health, node status, test run trends, browser grid availability, and platform activity — all in one place.
Access
Who can access: All logged-in users.
How to navigate there: Click the Deployment Dashboard icon (network hub icon) in the main navigation bar. A dropdown menu appears with the following sections:
| Section | Description |
|---|---|
| Dashboard | Platform-wide summary |
| Activities | Chronological event log |
| Devices | Device list and device dashboards |
| Browsers | Browser/Selenium grid nodes |
| Nodes | Node list and node dashboards |
| Connect Nodes | Local device connection nodes |
| Jobs | All jobs across the platform |
| Session | All active and recent sessions |
| Job Analysis | Job-level trend analysis |
| Failure Analysis | Failure pattern analysis |
| Secret Tokens | Manage secret tokens |
1. Dashboard Overview
The main Dashboard view gives a high-level summary of platform-wide status including connected devices, active nodes, running jobs, and recent activity.
2. Device Dashboard
The Device Dashboard shows operational details and performance analytics for each device in your lab.
To open the Device Dashboard:
- Navigate to Product Dashboard > Devices.
- Click on any device to open its dashboard.
Device Information panel shows:
- Device name, model, and OS
- Current connection status
- Last connected and disconnected timestamps
Device Health Score is displayed as a badge on the device. The score is calculated from job pass/fail rates across recent test runs, with more recent jobs weighted higher. A higher score means the device has been performing well across recent test runs.
Device Analytics panels include:
| Panel | Description |
|---|---|
| Up/Down Time | Timeline of device connection and disconnection events |
| Test Run Analysis | Pass/fail/error breakdown of jobs run on this device |
| Device Session | History of test sessions executed on the device |
| Device Preparation Failures | Count and details of failures during device preparation (app install, reset) |
WiFi History shows a log of WiFi network changes on the device, including the network name, signal strength, and timestamp of each change. This is useful for diagnosing connectivity-related test failures.
3. Node Dashboard
The Node Dashboard shows status and performance metrics for each RobusTest node (the machines that host your devices).
To open the Node Dashboard:
- Navigate to Product Dashboard > Nodes.
- Click on any node to open its dashboard.
Node Information panel shows:
- Node name, host, and OS
- Current connection status
- Node ID
Node Analytics panels include:
| Panel | Description |
|---|---|
| Up/Down Time | Timeline of node connection and disconnection events |
| Node Session | Test sessions executed through this node |
4. Browser / Grid Dashboard
The Browser Dashboard provides visibility into your Selenium grid infrastructure — the browser nodes and available browser instances for web testing.
To access: Navigate to Product Dashboard > Browsers.
- Lists all connected browser nodes with host, status, and available browser types
- Click on a browser node to see its detailed dashboard including session history and uptime
5. Run Analysis Dashboard
The Run Analysis Dashboard shows trends and patterns across all test jobs executed on the platform over a selected time period.
To access: Navigate to Product Dashboard > Run Analysis.
Use the Duration Filter to select the time window (e.g. last 7 days, last 30 days, or a custom date range).
The dashboard displays aggregated metrics across all jobs in the selected period, helping you identify trends in test stability, device utilisation, and failure patterns over time.
6. Activities
The Activities view provides a chronological log of all significant events on the platform — device connections, job submissions, user actions, and system events.
To access: Navigate to Product Dashboard > Activities.
Use this view to audit platform usage, investigate incidents, or track when specific actions were taken.