Framework for testing third-party JavaScript applications
Latest commit 14f0d90 May 17, 2012 @valueof Fix a bug with Hiro running all suites even though we want just one
Yesterday I made a change that showed only the suite we wanted if
you specify its name in a querystring. But I forgot to update Hiro
itself to ignore all other suites so, as the result, today you
would *see* just one suite while Hiro would *run* all suites behind
the scenes. This patch fixes that.



Hiro is a framework for testing third-party JavaScript applications.
It runs each test suite in a separate sandbox preventing global state
leaks and conflicts.

Stable version can be found here: The current
*master* branch contains the source of Hiro 2, backwards incompatible
iteration of Hiro that is scheduled to be released soon.


Before submitting a patch please make sure that:

  0) You have an issue opened describing your problem or proposal.
  1) You use tabs for indentation.
  2) Your coding style looks similar to what is already in the repo.
  3) All JavaScript files pass JSHint check (you can run 'grunt lint'
     to automatically lint files.
  4) All tests pass. To run tests open 'tests/test.html' in your
  5) Example tests behave as intended. To check that execute 'grunt run'
     and open http://localhost:7777/ in your browser. Execute all tests
     and you should see only three failures:

       * BasicTests.testFailedTest
       * Basictests.testFailedExpect
       * FailedSuite.testSimple

     These failures were introduced for UI demonstration purposes.
  6) Your commit messages look good (no one-liners please). See most
     recent commit messages for reference.


Anton Kovalyov