QUnit is especially useful for regression testing: Whenever a bug is reported, write a test that asserts the existence of that particular bug. Then fix it and commit both. Every time you work on the code again, run the tests. If the bug comes up again - a regression - you'll spot it immediately and know how to fix it, because you know what code you just changed.
Having good unit test coverage makes safe refactoring easy and cheap. You can run the tests after each small refactoring step and always know what change broke something.
If you are interested in helping developing QUnit, you are in the right place. For related discussions, visit the QUnit and Testing forum.
Planning for a qunitjs.com site and other testing tools related work now happens on the jQuery Testing Team planning wiki.
To submit patches, fork the repository, create a branch for the change. Then implement
the change, run
grunt to lint and test it, then commit, push and create a pull request.
Include some background for the change in the commit message and
Fixes #nnn, referring
to the issue number you're addressing.
grunt, you need
npm install grunt -g. That gives you a global
grunt binary. For additional grunt tasks, also run
Install git-extras and run
git changelog to update History.md.
Update qunit/qunit.js|css and package.json to the release version, commit and
tag, update them again to the next version, commit and push commits and tags
git push --tags origin master).
Put the 'v' in front of the tag, e.g.
v1.8.0. Clean up the changelog, removing merge commits
or whitespace cleanups.
To upload to code.jquery.com (replace $version accordingly):
scp -q qunit/qunit.js email@example.com:/var/www/html/code.jquery.com/qunit/qunit-$version.js scp -q qunit/qunit.css firstname.lastname@example.org:/var/www/html/code.jquery.com/qunit/qunit-$version.css
Then update /var/www/html/code.jquery.com/index.html and purge it with:
curl -s http://code.origin.jquery.com/?reload