zulip/tools/test-js-with-node

#!/bin/bash -e

cd "$(dirname "$0")"/..

export NODE_PATH=/usr/lib/nodejs:static

INDEX_JS=zerver/tests/frontend/node/index.js
NODEJS=$(which nodejs || which node)
if [ f$1 = fcover ]; then
  # Run a coverage test with Istanbul.
  istanbul cover $INDEX_JS
else
  # Normal testing, no coverage analysis.
  # Run the index.js test runner, which runs all the other tests.
  $NODEJS --stack-trace-limit=100 $INDEX_JS
fi
Run node-based JS unit tests from test-all (imported from commit 5bf9b690dfd3ac83296a58cf44a170960adaed39) 2013-07-26 20:31:24 +02:00			`#!/bin/bash -e`

Add a Node.js-based test runner There are no functional changes; you can still use the shell script tools/test-js-with-node. It just delegates now to the new index.js to iterate through all the other .js files in the test directory and run them. This sets the stage for Istanbul to correctly compute test coverage. (imported from commit 6f521c78b7a314d010fa113f9c2c971ab999b637) 2013-08-20 06:15:41 +02:00			`cd "$(dirname "$0")"/..`
Account for nodejs sometimes being installed as 'node' and sometimes as 'nodejs' (imported from commit 751216c9544671106dd555823e31ad9d4553a7aa) 2013-07-27 00:03:46 +02:00
Include /usr/lib/nodejs in node search path. (imported from commit c818905a91a5fe5754a0bddeb12caa00b50bfed3) 2013-12-02 23:46:09 +01:00			`export NODE_PATH=/usr/lib/nodejs:static`
Add the "static" directory to NODE_PATH for unit tests. I added our "static" directory to NODE_PATH for our JS unit tests. This eliminates most of the verbosity in our require statements, but it still requires us to explicitly call out "js" or "third" subdirectories, which should make it a bit easier for folks reading the tests to distinguish modules from js, third, or node itself. (imported from commit b77a5283135d388d46f4b7e511acc59986f1a8ba) 2013-08-01 17:53:10 +02:00
Add a Node.js-based test runner There are no functional changes; you can still use the shell script tools/test-js-with-node. It just delegates now to the new index.js to iterate through all the other .js files in the test directory and run them. This sets the stage for Istanbul to correctly compute test coverage. (imported from commit 6f521c78b7a314d010fa113f9c2c971ab999b637) 2013-08-20 06:15:41 +02:00			`INDEX_JS=zerver/tests/frontend/node/index.js`
test-js-with-node: Fix searching for node binary Previously, when the first `which` failed, the entire script would fail with exist status 1 because we pass `-e` to the interpreter. (imported from commit 601de3b3e3edd90110fc478f7874e644009d1b62) 2013-07-30 23:54:33 +02:00			`NODEJS=$(which nodejs \|\| which node)`
Add support for analyzing test coverage with Istanbul To use, make sure your Node installation is up to date and install istanbul with npm: sudo npm install -g istanbul # 'sudo' may be optional on OSX Then run tools/test-js-with-node cover and navigate to coverage/lcov-report/js/index.html in a browser. (imported from commit 2da4894d1725e2f9540b3895304246e3cd138f6c) 2013-08-20 06:20:02 +02:00			`if [ f$1 = fcover ]; then`
			`# Run a coverage test with Istanbul.`
			`istanbul cover $INDEX_JS`
			`else`
			`# Normal testing, no coverage analysis.`
			`# Run the index.js test runner, which runs all the other tests.`
Have better stack traces for node tests. (imported from commit 7053852dcd1b8479f1dbcb8cf7e46f008afe8a5a) 2014-02-10 19:06:13 +01:00			`$NODEJS --stack-trace-limit=100 $INDEX_JS`
Add support for analyzing test coverage with Istanbul To use, make sure your Node installation is up to date and install istanbul with npm: sudo npm install -g istanbul # 'sudo' may be optional on OSX Then run tools/test-js-with-node cover and navigate to coverage/lcov-report/js/index.html in a browser. (imported from commit 2da4894d1725e2f9540b3895304246e3cd138f6c) 2013-08-20 06:20:02 +02:00			`fi`