Getting Started

In Node.js

Getting Started in Node.js

In the browser

Getting Started in the browser

Guides

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

1. QUnit.module: How to group related tests.
2. QUnit.test: Define tests, How to wait for async code.
3. Fixture feature: Keeping your DOM tests atomic.
4. Step API: Testing asynchronous callbacks or event listeners.
5. Assertions: Partial object comparison, expected exceptions, and much more.
6. Browser: Productivity tricks, Browser automation, What can the toolbar do?
7. CLI: Productivity tricks, Code coverage.
8. Reporter API: Event emitter, Create your own reporter.
9. Theme API: Create your own theme.

Compatibility

QUnit supports the following runtime environments:

Desktop and mobile browser support

	QUnit 1	QUnit 2	QUnit 3	QUnit 3 (ESM)
Internet Explorer	IE 6-11	IE 9-11		—
Microsoft Edge	1+	15+[?]		16+
Firefox	3.6+	45+		60+
Safari	4.0+	9.1+		10.1+
Mobile Safari (iOS)	4.0+	7.0+		10.3+
Chrome	1+	58+		61+
Chrome Mobile	—	49+ (Android 4.4+)		61+ (Android 7+)
Opera	11+	36+		48+
Android Browser	2.3 - 5.0	4.3 - 5.0		—

QUnit can also be run in a sandboxed iframe (since 2.2), and in Web Worker threads (since 2.3).

Server runtime support

	QUnit 1	QUnit 2	QUnit 3	QUnit 3 (ESM)
PhantomJS	1.x		—
Node.js	—	10+	18+
SpiderMonkey (mozjs)	—	68+[?]

You can download QUnit 1.x and QUnit 2.x from the release archives.

Support

To report a bug, request a new feature, or ask a question open an issue on GitHub.

You can also find support on StackOverflow. Use the “qunit” hashtag on StackOverflow to search existing questions or ask your own question.

Chat

If you need help, or want to participate in sharing and discussing ideas, join us in the chat room on Matrix at #qunitjs_qunit:gitter.im:

• Gitter web client, browse the room as guest.
• Element web client, join and log in (with GitHub, GitLab, Google, or Apple ID), or sign up.
• matrix.to link, join with the Element native app or other Matrix client.

Social media

Follow us:

• Mastodon: @qunit@fosstodon.org
• Bluesky: @qunitjs.com

Hashtags:

• Mastodon: #qunit
• Bluesky: #qunit
• Threads: #qunit

---

Linting

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

---

Download

These are the official release channels for QUnit releases:

• Download:

  You can save the qunit-2.26.0.js and qunit-2.26.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.26.0.css'
  curl -o qunit.js 'https://code.jquery.com/qunit/qunit-2.26.0.js'
  

• npm Registry:

  If your development workflow uses Node.js, you can install the qunit package from the npm Registry, using the npm CLI:

  npm install --save-dev qunit
  

  Or, if using Yarn:

  yarn add --dev qunit
  

  You can then reference these in your HTML:

  <link rel="stylesheet" href="./node_modules/qunit/qunit/qunit.css">
  <script src="./node_modules/qunit/qunit/qunit.js"></script>
  

  If your project uses an npm alternative 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.

---

Further reading

• Read QUnit documentation offline, via DevDocs.
• Introduction to JavaScript Unit Testing, Jörn Zaefferer (2012).