Getting Started

In Node.js

Check these QUnit tutorials and examples, to make the most of your unit tests!

To report a bug or request a new feature, open an issue.

If you need help using QUnit, join us in the Matrix chat!

The eslint-plugin-qunit package has a variety of rules available for enforcing best testing practices as well as detecting broken tests.

These are the official release channels for QUnit releases:

Download:

You can save the qunit-2.22.0.js and qunit-2.22.0.css files directly from the jQuery CDN. For older versions, browse the release archives.

Or download them via the terminal, and save them in your Git repository.
```
curl -o qunit.css 'https://code.jquery.com/qunit/qunit-2.22.0.css'
curl -o qunit.js 'https://code.jquery.com/qunit/qunit-2.22.0.js'
```
npm Registry:

If your development workflow uses Node.js, you can install the qunit package the npm Registry, using the npm CLI:
```
npm install --save-dev qunit
```
Or, if using Yarn:
```
yarn add --dev qunit
```
You can then reference node_modules/qunit/qunit/qunit.css and node_modules/qunit/qunit/qunit.js in your HTML.

If your project uses a custom npm frontend that locates packages elsewhere, you may need to generate the HTML dynamically and use require.resolve() to locate qunit/qunit/qunit.js and qunit/qunit/qunit.css. Alternatively, use one of the Integrations such as karma-qunit which can do this for you.
Bower:

QUnit 1.x and QUnit 2.x releases were published to Bower, and remain available there under the qunit package.

For QUnit 3.0 and later, either download and commit the JS and CSS file directly in your project (e.g. using the curl command above), or install the qunit package from npm as a dev dependency.