Testing HOWTO

In order to facilitate problem solving it helps to have a consistent way of communicating test results.

Please first review our Debug HOWTO and make sure you have the -dbg packages installed.

Below we describe the most common scenarios and how they are best tested (with full logging).

In the test we have two participants. We call them A (The caller, who initiate the communication) and B (The callee, who is on the receiving end of the action).

Initial setup before testing starts

On both client A and client B, run the command:

GST_DEBUG=3 G_MESSAGES_DEBUG=all NICE_DEBUG=all,libnice-nice-verbose pidgin --debug |& tee ~/pidgin.log

Test video

1. Activate logging in a separate terminal on each client.

On client A:

tail -f ~/pidgin.log |& tee ~/test-video-A.log

On client B:

tail -f ~/pidgin.log |& tee ~/test-video-B.log

2. Test. Let client A call client B.

3. Conclude. Stop logging with <ctrl>-c in the respective terminal windows where the tail-commands are running.

4. Now you have two nice log files, test-video-A.log and test-video-B.log you can send to us.

Test Desktop Screen Sharing

1. On client B, start remmina in a gdb-session

   (gdb) file remmina Reading symbols from remmina...Reading symbols from /usr/lib/debug/.build-id/52/55f707a2b9d5dc65776effa6678b8a3b9650ad.debug...done. done. (gdb) run Starting program: /usr/bin/remmina ...

2. Activate logging in a separate terminal on each client.

On client A:

tail -f ~/pidgin.log |& tee ~/test-screensharing-A.log

On client B:

tail -f ~/pidgin.log |& tee ~/test-screensharing-B.log

2. Test. Let client A share the desktop with client B.

3. Conclude. Stop logging with <ctrl>-c in the respective terminal windows where the tail-commands are running.

4. Now you have two nice log files, test-screensharing-A.log and test-screensharing-B.log you can send to us. And should the screen sharing session crash, you can catch the output from the gdb-session running on client B with:

   bt full