Manual Testing with WebRTC
RobusTest manual test sessions use WebRTC for low-latency peer-to-peer device streaming. No plugins or additional setup are required.
Supported Platforms
- Android — streamed via scrcpy with configurable quality. Audio requires Android 8.0 (SDK 26) or later.
- iOS — streamed via native frame capture at 20 FPS.
Starting a Session
No additional steps are required. Start a manual test session from the Project Dashboard and the WebRTC connection is established automatically.
You can also open a session directly using the session URL:
<RobusTest URL>/#/screen/testsession/<testsessionID>
Replace <testsessionID> with the ID of your active test session. This URL can be shared with teammates to give them a direct link to the live session view.
Stream Quality (Android)
When starting a session on an Android device, you can select a stream quality profile. The default is Low.
| Profile | Resolution | Bitrate | Frame Rate |
|---|---|---|---|
| Ultra Low | 480p | 1 Mbps | 24 fps |
| Low (default) | 720p | 4 Mbps | 30 fps |
| Balanced | 1080p | 8 Mbps | 30 fps |
| Medium | 1080p | 15 Mbps | 60 fps |
| High | Full resolution | 30 Mbps | 60 fps |
| Ultra | Full resolution | 50 Mbps | 60 fps |
Note: Higher quality profiles require more network bandwidth. Use Ultra Low or Low for remote or bandwidth-constrained environments.
Session Status Messages
During session startup, status messages are displayed in the session interface:
| Message | Meaning |
|---|---|
| Starting scrcpy server | Initialising the device screen capture process |
| Waiting for scrcpy connections | Screen capture process is connecting to the device |
| Scrcpy connected | Device screen capture is established |
| Video streaming active | Stream is live and being sent to the browser |
| Stream stopped | Session has ended or been closed |
If you see an error during startup, wait a few seconds and attempt to reconnect. The device stream is kept alive across reconnection attempts.