Skip to content

croasus/jub.dj

Folders and files

NameName
Last commit message
Last commit date

Latest commit

8e16eb8 · Aug 27, 2017
Aug 15, 2017
Nov 7, 2016
Jan 12, 2016
Aug 27, 2017
Sep 22, 2016
Jul 5, 2017
Nov 18, 2016
Jul 5, 2017
Jul 5, 2017
May 10, 2016
Nov 6, 2016
Jan 16, 2017
Jul 11, 2017
Jul 5, 2017
Jan 28, 2017

Repository files navigation

thejub.pub

chat + shared video

Build Status

thejub.pub screenshot

Setup

  1. Clone this repo
  2. Install node.js + npm
  1. Install the dependencies. From the project directory: $ npm install --loglevel verbose

  2. Copy the example config.js under example/ to the root level: $ cp example/config.js config.js

  3. Get YouTube developer keys (you'll have to get one for server and one for browser) and replace google_api_server_key and google_api_browser_key with the ones provided by Google.

Running the server

The server can be started with the following command:

$ TEST=1 JUB_CONFIG=test/config.js npm start

Then visit http://localhost:3000/ROUTE in your browser, where ROUTE is the value of "private_route" in config.js. You can specify a different port number using the PORT environment variable.

Testing

Tests are slowly being added. To run them:

$ npm test

There are two sets of tests: server (unit/functional) tests and UI (integration/end-to-end) tests.

Adding a UI test

The UI tests use Selenium via Nightwatch. See the tests in test/ui/.

The quickest way to iterate is to start the Selenium server manually and then run only your test case, instead of the entire test suite:

# In one shell:
$ ./test/bin/start-selenium

# In another shell:
$ ./test/bin/run-ui-test YOUR_UI_TEST

Adding a library test

To add a new test, add a script to the test/server/ directory. It should be a node.js script, and should output something meaningful (i.e., so that if the relevant feature broke, your test's output would change).

While developing your test, make sure to run your script with environment variable TEST=1.

Once your test is producing the correct output, run the baseline tool to create its baseline file:

$ node test/bin/baseline.js -b YOUR_TEST

Next, run the baseline tool with no arguments to make sure the other server tests still pass. If any of the tests fail, it means their output has changed. If in fact their new output is now correct, then rewrite their baselines (using -b as above). Don't forget to commit your new test and its baseline.

Known issues

Internet Explorer is currently not supported.

About

chat + shared video

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published