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.
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 Node.js, which includes
npm install -g grunt-cli. That gives you a global grunt binary. For additional grunt tasks, also run
Use jquery-release. The following aren't handled there, do that first:
git changelogto update
History.md. Clean up the changelog, removing merge commits, whitespace cleanups or other irrelevant commits.
grunt authorsand add any new authors to AUTHORS.txt
package.jsonto have the right -pre version. Not necessary for patch releases.
Build: Prepare @VERSION release, including authors and history update
Then run the script:
node release.js --remote=jquery/qunit
jquery/qunitjs.com, replacing previous versions with new ones:
Update GitHub releases, use the changelog from
Finally announce on Twitter @qunitjs (add highlights if possible, otherwise a 2nd tweet might do):
Released @VERSION: https://github.com/jquery/qunit/releases/tag/1.17.0