468516c959
host that controls multiple endpoints ("bots"). Thus allowing to create more
complex scenarios that would otherwise require non-trival signalling between
multiple parties.
R=houssainy@google.com, phoglund@webrtc.org
Review URL: https://webrtc-codereview.appspot.com/22239004
git-svn-id: http://webrtc.googlecode.com/svn/trunk@7021 4adac7df-926f-26a2-2b94-8c16560cd09d
28 lines
982 B
Plaintext
28 lines
982 B
Plaintext
=== RTCBot ===
|
|
RTCBot is a framework to write tests that need to spawn multiple webrtc
|
|
endpoints.
|
|
|
|
== Description ==
|
|
RTCBot is a framework that allows to write tests where logic runs on a single
|
|
host that controls multiple endpoints ("bots"). It allows creating complex
|
|
scenarios that would otherwise require non-trival signalling between multiple
|
|
parties.
|
|
|
|
The host runs in node.js, but the test code is run in an isolated context with
|
|
no access to node.js specifics other than the exposed api via a test variable.
|
|
|
|
Part of the exposed api (test.spawnBot) allows a test to spawn a bot and
|
|
access its exposed API. Details are in BotManager.js.
|
|
|
|
== How to run the test ==
|
|
$ cd trunk/webrtc/tool/rtcbot
|
|
$ npm install express browserify ws websocket-stream dnode
|
|
$ node test.js
|
|
|
|
== Example on how to install nodejs ==
|
|
$ cd /work/tools/
|
|
$ git clone https://github.com/creationix/nvm.git
|
|
$ export NVM_DIR=/work/tools/nvm; source $NVM_DIR/nvm.sh
|
|
$ nvm install 0.10
|
|
$ nvm use 0.10
|