Skip to content

/qunit

An easy-to-use JavaScript Unit Testing framework.
qunit testing javascript
  1. JavaScript 93.6%
  2. HTML 4.5%
  3. CSS 1.9%
Branch: master
Find File
Clone or download

Clone with HTTPS

Use Git or checkout with SVN using the web URL.

Download ZIP

Launching GitHub Desktop...

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop...

If nothing happens, download GitHub Desktop and try again.

Launching Xcode...

If nothing happens, download Xcode and try again.

Launching Visual Studio...

If nothing happens, download the GitHub extension for Visual Studio and try again.

@ghaagsma @stefanpenner
ghaagsma and stefanpenner Display progress and runtime while test suite is executing (#1398) 
Closes #1394
Latest commit cc1fdb6 Jun 19, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Readme: Add ISSUE_TEMPLATE with issue guidelines to repository (#1104) Feb 27, 2017
bin Build: Fix (and add tests) missing required files in 2.9.0. (#1368) Jan 7, 2019
build Build: Upgrade grunt-contrib-qunit to 3.x (Headless Chrome) Aug 20, 2018
docs Doc: deepEqual() checks strict inherited equality Feb 26, 2019
reporter Display progress and runtime while test suite is executing (#1398) Jun 18, 2019
runner HTML Reporter: Ensure attributes on qunit-fixture are reset. Jan 17, 2018
src CLI: Ignore those folders mentioned in the gitignore Jun 14, 2019
test Display progress and runtime while test suite is executing (#1398) Jun 18, 2019
.babelrc Build: Use babel-preset-env and .babelrc Dec 15, 2017
.editorconfig Build: Add .editorconfig for common editor settings Feb 23, 2014
.eslintrc.json Build: Set "root: true" in eslintrc Jan 7, 2019
.gitattributes Tests: HTML files should end with LF Dec 5, 2016
.gitignore Docs: Migrate api docs (#1135) Mar 31, 2017
.mailmap Build: Prepare 2.9.0 release, including authors and history update Jan 6, 2019
.travis.yml Build: Add macOS and Windows to the Travis CI test matrix (#1360) Jan 2, 2019
AUTHORS.txt Build: Prepare 2.9.2 release, including authors and history update Feb 21, 2019
CODE_OF_CONDUCT.md All: Add CODE_OF_CONDUCT pointing to the JS Foundation code of conduct Sep 30, 2018
CONTRIBUTING.md Docs: Update README/CONTRIBUTING with more recent/relevant information May 29, 2017
Gruntfile.js Build: Add macOS and Windows to the Travis CI test matrix (#1360) Jan 2, 2019
History.md Build: Prepare 2.9.2 release, including authors and history update Feb 21, 2019
LICENSE.txt All: Update License to JSFoundation Nov 1, 2016
README.md Docs: Update Travis badge Mar 1, 2019
RELEASE.md Docs: Add a few missing steps to release docs Feb 22, 2019
bower.json Build: Use SPDX format in bower.json's license Sep 6, 2016
package.json Build: Update node-watch to 0.6.1 Apr 14, 2019
rollup.config.js Core: Adding promise handling on qunit callbacks: begin, moduleStart,… Nov 1, 2018
yarn.lock Build: Update node-watch to 0.6.1 Apr 14, 2019

README.md

Build Status Coverage Status Chat on Gitter FOSSA 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, such as built in support for asynchronicity and exception handling.

Support

If you need help using QUnit, visit the QUnit and Testing forum or chat with us on Gitter.

If you believe there is a bug with QUnit or would like to request a new feature, open an issue.

Development / Contributions

If you are interested in helping develop QUnit, check out our contributing guide.

You can’t perform that action at this time.