-
Notifications
You must be signed in to change notification settings - Fork 24
Testing HOWTO
Niklas Andersson edited this page May 3, 2016
·
12 revisions
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).
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
- 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
-
Test. Let client A call client B.
-
Conclude. Stop logging with
ctrl-C in the respective terminal windows where the tail-commands are running. -
Now you have two nice log files, test-video-A.log and test-video-B.log you can send to us.