* first cut at JS unit tests using QUnit --- made some tests of the
  Api JS module that work correctly iff it's okay to load data from
  the live DB (which it is for Api.getButtonData(), but not really
  for Api.getPlayerData())
* also modify the README to involve copying the tests over
* use dummy_responder.php when unit tests are being run, and responder.php otherwise
Merge branch 'master' of github.com:buttonmen-dev/buttonmen into 232_qunit
* add mostly-stubbed-out dummy responder with enough contents that the Api.js tests now pass
* start test_Env module, and introduce an audit script for test coverage of all functions
* finish code coverage audit script, and add (failing) checks until the auditer is happy
* implement remaining unit tests for Env module
* env test fix - clean up all objects which might have been created during testing
* add a teardown test for whether the DOM changed in any ways not expected by the Env module
* also test that there are no unexpected changes to javascript objects, and make Env and Api pass this test
* implement remaining passing tests for Api modules
* initial test of Game.parseGameData()
* partial implementation of Game.js tests
Merge branch 'master' of github.com:buttonmen-dev/buttonmen into 232_qunit
* complete initial tests for Game.js
* audit wrapper which runs all CLI-compatible audit/unit tests
* slightly refactor responder and dummy_responder to be class-based
  enough that they can be invoked without POST
* add regression tests of responder vs dummy_responder access
  syntax for most responder functions
* a couple of small Overview.js fixes -- bitrot in behavior when
  there are no games, and subideal function names
* add real unit tests for Overview module, and fake ones for Login, Newgame, and Newuser