Skip to content


Subversion checkout URL

You can clone with
Download ZIP
An easy-to-use JavaScript Unit Testing framework.
JavaScript HTML CSS

Build: Enable IRC notifications for Travis CI

Follows-up 0d52b8d, and d1564e1.

Also move 'sudo' to be on top because it controls which container
is used, more hierarchical in order.

Closes gh-853
latest commit 0c4fcd6d21
@Krinkle Krinkle authored
Failed to load latest commit information.
build Build: Actually dependencies must be an array
reporter Build: Remove unintended QUnit global export on Node
src Core: Optimize utilization of global and window variables
test Tests: Add tests for QUnit.diff
.editorconfig Build: Add .editorconfig for common editor settings
.gitattributes Build: Add .gitattributes to tell git to normalize linefeeds in JS files
.gitignore Test: Updating BrowserStack config to run all test pages
.jscsrc Build: Also disable onevar equivalent for jscs
.jshintrc Core: More graceful handling of AMD
.mailmap Authors: Fix a bad firstname, now matches CLA name
.travis.yml Build: Enable IRC notifications for Travis CI
AUTHORS.txt Build: Prepare 1.18.0 release, including authors and history update Docs: Removed IRC channel links in
Gruntfile.js Build: Move QUnit.diff inside intro/outro Build: Prepare 1.18.0 release, including authors and history update
LICENSE.txt HTML Reporter: New diff using Google's Diff-Patch-Match Library Readme: Replace Jenkins badge with Travis
bower.json Build: Remove bower.json from ignored files
browserstack-all.json Build: Update browserstack settings
browserstack.json Build: Update browserstack settings
package.json Build: Add 'Readme' to commitplease components

Build Status Coverage Status

QUnit - A JavaScript Unit Testing Framework.

QUnit is a powerful, easy-to-use, JavaScript unit testing framework. It's used by the jQuery project to test its code and plugins but is capable of testing any generic JavaScript code (and even capable of testing JavaScript code on the server-side).

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.

QUnit is similar to other unit testing frameworks like JUnit, but makes use of the features JavaScript provides and helps with testing code in the browser, e.g. with its stop/start facilities for testing asynchronous code.

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.

To run grunt, you need Node.js, which includes npm, then npm install -g grunt-cli. That gives you a global grunt binary. For additional grunt tasks, also run npm install.


Use jquery-release. The following aren't handled there, do that first:

  • Install git-extras and run git changelog to update Clean up the changelog, removing merge commits, whitespace cleanups or other irrelevant commits.
  • Run grunt authors and add any new authors to AUTHORS.txt
  • Update the version property in package.json to have the right -pre version. Not necessary for patch releases.

Commit these:

Build: Prepare @VERSION release, including authors and history update

Then run the script:

node release.js --remote=jquery/qunit

Update jquery/, replacing previous versions with new ones:

  • pages/index.html
  • resources/*.html

Update GitHub releases, use the changelog from

Finally announce on Twitter @qunitjs (add highlights if possible, otherwise a 2nd tweet might do):

Released @VERSION:
Something went wrong with that request. Please try again.