JS TestNet is a Django web service that coordinates the execution of JavaScript tests across web browsers. It was designed to run pure JavaScript tests with Qunit in a CI environment like Jenkins and to get test feedback from real web browsers. It is probably flexible enough for other JavaScript test runners too.
First, you need Python 2.5 or greater. Clone this repository, create a virtualenv, then cd into the project and run:
pip install -r requirements.txt
pip install -r requirements/compiled.txtMake your own settings_local.py:
cp settings_local.py-example settings_local.pySet up a MySQL user and database:
mysql> create user jstestnet_dev@localhost identified by 'test';
mysql> create database jstestnet_dev;
mysql> grant all on jstestnet_dev.* to jstestnet_dev;Then enter the credentials in settings_local.py:
DATABASES['default']['NAME'] = 'jstestnet_dev'
DATABASES['default']['USER'] = 'jstestnet_dev'
DATABASES['default']['PASSWORD'] = 'test'Also in settings_local.py, uncomment the HMAC_KEYS setting and enter some unique value.
Create the database:
./manage.py syncdbDuring the process, you will be prompted to create a superuser. You should do so, or run the createsuperuser management command later.
./manage.py createsuperuserStart the server and open the front page to see the system status.
./manage.py runserverA test suite is a URL to an HTML page that runs tests in a web browser when loaded. The front page of the JS TestNet app links to a form where an administrator can add a test suite into the system.
You will have to make one modification to your test suite. It must include the jstestnet.js script (found in the adapter folder) to communicate with the worker. Be sure it loads after Qunit or whatever supported test runner you are using.
<html>
<head>
<title>Your QUnit Test Suite</title>
<script type="text/javascript" src="/js/jquery.js"></script>
<script type="text/javascript" src="/js/qunit/testrunner.js"></script>
<script type="text/javascript" src="/js/jstestnet.js"></script>
</head>
<body>
...
</body>
</html>This enables your test suite to send results back to JS TestNet via window.postMessage.
You will also need to be sure your web server is not sending a response header like this:
X-Frame-Options: DENYTo register a web browser to run the tests (called a worker) just open the browser and go to this URL and leave the window open:
http://127.0.0.1:8000/work/The worker will be able to run tests for as long as you keep that window open. In a CI environment you probably want to open this once in a virtual machine and forget all about it.
You can open this URL on any web enabled device and it will automatically join the work pool. For example, you could type this URL into your smart phone and your phone would become a worker.
To start your test suite on all web browsers, just request this URL from curl or a custom script (more on that later):
http://127.0.0.1:8000/start_tests/fooThat will return a JSON response of who is working on your tests. You can check for results at:
http://127.0.0.1:8000/job/{id}/resultCheck out JsTestNetLib!
This simple pub/sub model was inspired by jsTestDriver, which is a great tool for running very fast unit tests. JS TestNet set out with a different goal: run any kind of JavaScript tests, especially middle-tier integration tests that do not lock down your implementation as much as unit tests. You may want to mock out jQuery's $.ajax method and perform asynchronous Ajax calls -- go for it!
JS TestNet's worker implementation was forked from TestSwarm, which is a similar tool. JS TestNet is different in that it supports direct execution of tests suitable for CI. Big thanks to John Resig for figuring out a lot of the cross domain stuff and implementing retry timeouts, error handling, etc :) Also, JS TestNet is dumber than TestSwarm in that it requires an adapter.
Hi! Feel free to submit bugs, patches and pull requests on github. To run the test suite first install tox then run it from the project dir:
$ cd jstestnet
$ tox- Handle unexpected errors in the worker
- Add some kind of secure test execution to prevent DoS. Probably a simple token based thing.