Unit test assertions are backwards #6
Description
According to http://api.qunitjs.com/equal/, the first argument should be the result of the test's processing and the second one should be the expected result. Looks like the tests are all backwards, meaning if they fail they'll label the expected result the actual result and the actual result the expected result, which could be confusing.
(Note that pull requests #3 and #5 add some tests, but do not address this issue.)