Video call exploration

1. Talkilla currently requires Firefox > 23.

2. Make sure you have node installed.

3. Install the required node dependencies:

    $ npm install
    # or alternatively:
    $ make install
   

4. Start the server:

    $ env PORT=5000 node app.js
    # or alternatively:
    $ make runserver
   

5. In Firefox, set media.navigator.permission.disabled to true

6. Point your web browser to http://localhost:5000.

App configuration is done using JSON files stored in the config/ directory:

• dev.json for the dev environment configuration
• prod.json for the prod environment configuration
• local.json for any settings you may want to override locally (this file is never versionned)

Settings are:

• DEBUG: to have log messages printed out to the browser console
• WSURL: the url to the WebSocket server endpoint

To run the unit tests:

1. Make sure you've installed node and the required modules as per the local development section.

2. On Mac, you need to have /Applications/FirefoxNightly.app installed (aka Firefox 24)

3. On Linux, you need to have /usr/bin/firefox-nightly present, or a Firefox will be downloaded for you.

4. Run the tests:

    $ make test
   

To run the front-end unit tests standalone:

1. First make sure you are running the server in development mode:

   $ make runserver_dev

2. Visit http://localhost:5000/test/frontend/index.html

It can useful to execute individual functional tests in the Node debugger. Example usage:

1. (add a "debugger;" statement to the code where you want the debugger to break)

2. SOLO_FILE=chatwindow_test.js make debug_test

3. (debug)
4. (remove the debugger statement)

Note that because most of the things in the webdriver-selenium API that look like imperative statements are actually magic things that cause most of the semantics of the commands be enqueued by the ControlFlow piece of the "promise manager" to be executed at some point in the future. It can take some experimenting to figure out where to usefully put the debugger statements. It may be particularly useful to add a then() handler to the first promise-returning statement in the test you want to debug and put the debugger statement there.

https://code.google.com/p/selenium/wiki/WebDriverJs#Writing_Tests has more details on how this stuff fits together.

Look for a file named CONTRIBUTING.md in this repository. It contains our contributing guidelines.

All source code here is available under the MPL 2.0 license, unless otherwise indicated.