Older Webkit browsers (such as QtWebkit used in PhantomJS) don't have function.prototype.bind.

Use a polyfill from
https://developer.mozilla.org/en-US/docs/JavaScript/Reference/Global_Objects/Function/bind
Older Webkit browsers (such as QtWebkit used in PhantomJS) don't have window.requestAnimationFrame

Fake it using window.setTimeout.
Fixes for the latest version of Firefox.
Add posting of the results to the HTTP server.
Start of a python based test-runner.

Current set of features:
 * Spawns a local HTTP server to serve the tests and capture the results.
 * Uses selenium to fire up a browser and run the tests.
 * Downloads the needed Python packages automagically if needed.
 * Downloads the needed driver support binaries if needed.
 * Supports Chrome, Firefox and PhantomJS.
 * Supports the subunit protocol for output (can be use with testrepository).
 * Support for running a virtual display if needed.

Things coming
 * Should support IE under windows.
 * Support Android/IPhone.
 * Support running on "Selenium Grid".
 * Support for specifying Chrome/Firefox binary.

Basic usage
 ./run-tests.py -b PhantomJS

PhantomJS is the fastest test runner (~10s), followed by Chrome (~20s) and then
Firefox (~30s).
Install Python packages to the user instead of globally.
Removing a sperious print.
Using the testtools output rather then unittest.
Merge branch 'master' of git+ssh://github.com/mithro/web-animations-js
Capture all info about tests.
Adding a .travis.yml for CI.
Merge pull request #1 from rbtcollins/master

Capture data about tests.
Use input json rather then simplejson.
Trying to make builder work better.
Adding a .keepme for the tools directory.
Changing the way the requirements/imports work.
pyscreenshot is needed by pyvirtualdisplay but not installed automatically.
Output message rather then json information.
Give more information when auto-installing.
Changing auto-install to look at the .requirements file.

Keep all the requirements in only one location seems a good idea.