Media/WebRTC/Testing: Difference between revisions
Jump to navigation
Jump to search
Line 14: | Line 14: | ||
* media/mtransport — the mtransport generic transport subsystem and associated utilities | * media/mtransport — the mtransport generic transport subsystem and associated utilities | ||
* media/webrtc/signaling/test — the signaling system and the media handling system | * media/webrtc/signaling/test — the signaling system and the media handling system | ||
As usual, you can run them individually by doing: | As usual, you can run them individually by doing: | ||
Revision as of 23:03, 28 April 2013
WebRTC Test System
We currently test WebRTC with two sets of tests:
- Standalone C++ unit and system tests.
- Full system mochitests.
C++ Unit Tests
The WebRTC code has extensive C++ unit and system tests based on the [| Google Test] framework. These tests live in two locations:
- media/mtransport — the mtransport generic transport subsystem and associated utilities
- media/webrtc/signaling/test — the signaling system and the media handling system
As usual, you can run them individually by doing:
make -C <directory>
Alternately, you can run a single C++ unit test by name, e.g.,
media/mtransport/test/ice_unittest
Tinderbox runs all the tests in a given directory but for a variety of reasons some of the tests aren't run on Tinderbox. This is controlled by requiring certain environment variables to be set. For instance, if you just run signaling_unittests you get:
To run this test set MOZ_WEBRTC_TESTS=1 in your environment
Additionally, the TURN tests require you to specify a TURN server. This is done by setting:
TURN_SERVER_ADDRESS TURN_SERVER_USER TURN_SERVER_PASSWORD