README
1This test client is a simple functional test for WebRTC enabled Chrome build.
2
3The following is necessary to run the test:
4- A WebRTC Chrome binary.
5- A peerconnection_server binary (make peerconnection_server).
6
7It can be used in two scenarios:
81. Single client calling itself with the server test page
9(peerconnection/samples/server/server_test.html) in loopback mode as a fake
10client.
112. Call between two clients.
12
13To start the test for scenario (1):
141. Start peerconnection_server.
152. Start the WebRTC Chrome build: $ <path_to_chome_binary>/chrome
16--enable-media-stream --enable-p2papi --user-data-dir=<path_to_data>
17<path_to_data> is where Chrome looks for all its states, use for example
18"temp/chrome_webrtc_data". If you don't always start the browser from the same
19directory, use an absolute path instead.
203. Open the server test page, ensure loopback is enabled, choose a name (for
21example "loopback") and connect to the server.
224. Open the test page, connect to the server, select the loopback peer, click
23call.
24
25To start the test for scenario (2):
261. Start peerconnection_server.
272. Start the WebRTC Chrome build, see scenario (1).
283. Open the test page, connect to the server.
294. On another machine, start the WebRTC Chrome build.
305. Open the test page, connect to the server, select the other peer, click call.
31
32Note 1: There is currently a limitation so that the camera device can only be
33accessed once, even if in the same browser instance. Hence the need to use two
34machines for scenario (2).
35
36Note 2: The web page must normally be on a web server to be able to access the
37camera for security reasons.
38See http://blog.chromium.org/2008/12/security-in-depth-local-web-pages.html
39for more details on this topic. This can be overridden with the flag
40--allow-file-access-from-files, in which case running it over the file://
41URI scheme works.
42