Testing Marshall

The test files are included. (The spec files are in the test directory, apologies for not finding a cleverer name for the location.) The full test suite is controlled by the TestRunner.html file.

The testing environment I'm using is Jasmine 1.2 and I'm running tests both in the browser and via the command line using Phantomjs.

TestRunner.html is expecting the jasmine files to be in the jasmine/lib directory, except for the console-runner.js file -- I've modified the one shipping with phantom-jasmine to create a results report more to my liking, and included that modified one here in the jasmine/vendor directory. I'm not including the stock jasmine files in this project because if you already have them installed on your system, you don't need a second copy, and if you don't, getting them is easy, and you might want to place them somewhere common to all your projects, in order to test more than just Marshall.

Once you have jasmine installed (you can either install it in the jasmine directory here, or point the TestRunner.html file at wherever you have it installed) simply load TestRunner.html in the browser to test Marshall's performance against it.

(I should note at this point that some of the tests require support for document.getElementsByClassname(), so versions of IE before 9 will not be able to run the tests.)

If you find a bug that isn't covered by the test suite, add a test for it and send me a pull request so I can get it into the main testing tree to cover the bug for all future releases.