VNC can be used as an additional debugging tool that testRTC offers. It enables you to view how the browsers in a running test behave and to fix the test script accordingly.
To enable VNC support, you will first need to add #vnc as one of the run options of the test.
As a rule of thumb, don’t expect to see a VNC button in the following cases:
- If #vnc isn’t set in the run options
- If this is a scheduled monitor run
- If there are multiple probes running concurrently in this test you will see VNC on just two probes
- If VNC port resources on the physical machine are already allocated to other running tests – this may happen from time to time
Please Note that VNC takes up resources, and we can’t make it available on all running agents at once. Due to that, you may find that sometimes the VNC button doesn’t appear.
The VNC session is protected by a password. The password is ‘secret’.
VNC related issues
A: VNC takes up resources, and we can’t make it available on all running agents at once. Due to that, you may find that sometimes the VNC button doesn’t exist.
A: VNC is used for debugging purposes, so we don’t really optimize its use.
That said, there is one specific scenario in which you can expect VNC to work really bad – and that’s if you set the network configuration in a test to introduce packet loss. Since we configure the whole machine to simulate packet loss, the VNC connection on that machine suffers from the same problem.