QUnit
qunitjs.com
- Free plan
- Windows
- macOS
- Linux
- Web
- iPhone and iPad
- Android
- API
- Self-hosted
What QUnit is
QUnit is a free JavaScript testing framework that originated in the jQuery project. Developers can run it in web browsers, Node.js, SpiderMonkey and Web Worker threads to test code in its runtime environment. Its APIs allow custom assertions, test runners and reporters. Browser releases are standalone and have no runtime dependencies; the project describes Node.js setup as requiring zero configuration and browser setup as minimal. For DOM tests, QUnit resets fixture markup after each test. The browser reporter displays results and can show expected and actual values, assertion details and stack traces for failures. Developers can rerun selected tests or modules and prioritize previously failing tests. Asynchronous tests and callbacks are covered, and plugins can extend the framework with options such as DOM assertions, themes and JUnit XML reporters. Browser automation integrations listed include Karma, Web Test Runner, Testem and WebdriverIO’s QUnit service. QUnit 3.0 is distributed through the jQuery CDN and npm, and can also be installed with Yarn. Its ESM version lists Node.js 18+ and browser compatibility including Chrome 61+, Firefox 60+ and Safari 10.1+.
Who it suits
QUnit suits developers testing JavaScript in browsers, workers or server-side runtimes. It can also suit teams that need browser test reports or integrations with listed automation tools.
Good to know, and what to watch
- Runs in browsers, Node.js, SpiderMonkey and Web Workers
- Browser releases have no runtime dependencies
- Resets DOM fixture markup after each test
- Plugins can add assertions, themes and report formats
- QUnit 3 ESM requires Node.js 18+
- ESM browser support has listed version requirements
- Project work is done by volunteers
Plans
Every plan and priceQUnit
Free plan
Getting started
- Visit https://qunitjs.com/ for project information.
- Choose the jQuery CDN, npm, or Yarn distribution for QUnit 3.0.
- For local or offline development, install or download QUnit within the project.
- Use the zero-configuration Node.js setup or minimal browser setup described by the project.
- Follow the guides for modules, assertions, asynchronous tests, or DOM fixtures.
Limits to check
For the ESM version, QUnit 3 lists Node.js 18+ and browser compatibility including Chrome 61+, Firefox 60+, and Safari 10.1+.
The Club's review
QUnit is a JavaScript testing framework for developers who want to test code in browsers, workers, and server-side runtimes. It is strongest for projects that need DOM tests and useful browser failure reports; it is a narrower fit for teams looking beyond JavaScript.
Overview
Created for the jQuery project in 2008, QUnit runs in web browsers, Node.js, SpiderMonkey, and Web Worker threads. That range suits JavaScript projects spanning client and server environments, while its single-language focus rules it out as a shared testing framework for polyglot teams.
The framework covers test modules, asynchronous tests and callbacks, assertions, and parameterized cases, and supports parallel execution. The project describes Node.js setup as requiring no configuration and browser setup as minimal. Browser releases have no runtime dependencies, which makes a browser setup relatively lean. QUnit 3.0 is distributed through the jQuery CDN and npm, and can also be installed with Yarn. For offline development, the project recommends keeping a local copy in the project.
QUnit's APIs allow custom assertions, test runners, and reporters. Plugins can extend or modify the framework and developer experience, with examples including DOM assertions, themes, and JUnit XML reporters. The team says project work is done by volunteers; developers can seek help through GitHub issues, Stack Overflow, and a Matrix chat room.
Key features
Browser testing and debugging
The browser reporter presents results and can show expected and actual values, assertion details, and stack traces for failures. Resetting fixture markup after each test helps keep DOM cases isolated, reducing state leakage between tests. The runner can prioritize previously failing tests and rerun selected tests or modules, which helps developers focus on a regression without repeating an entire run.
Runtime and integration support
QUnit works across browsers, Node.js, SpiderMonkey, and Web Workers, so teams can use it for code that runs in more than one JavaScript environment. Browser automation integrations include Karma, Web Test Runner, Testem, and WebdriverIO's QUnit service. These options help fit QUnit into an automated browser workflow, though the framework itself remains focused on JavaScript rather than broader language coverage.
Compatibility
QUnit 3's ESM version requires Node.js 18 or later. Its compatibility guide also identifies Chrome 61+, Firefox 60+, and Safari 10.1+ for that version. Teams with older runtime or browser requirements should check those minimums before adopting the ESM release.
Pricing
QUnit is free, with a free plan priced at no cost. It is an open-source JavaScript testing framework distributed through the jQuery CDN, npm, and Yarn. There is no free trial because the framework is already available without charge. No paid tiers or seat-based plans are part of this offering, so it is suitable for individual developers and teams that need a no-cost framework; the trade-off is that its scope is JavaScript testing rather than a broader development platform.
Platforms
QUnit is listed for Android, iOS, Linux, macOS, self-hosted environments, the web, and Windows. Its runtime coverage includes browsers, Node.js, SpiderMonkey, and Web Workers. The JavaScript-only language support is the more important boundary for teams choosing it: platform breadth does not make it a multi-language testing tool.
Who it's for
QUnit is a good match for JavaScript developers who want to test code in the environment where it runs, especially when browser-based DOM tests and failure diagnostics are central. Minimal browser setup, zero-configuration Node.js use, and extensible assertions and reporters make it practical for projects that want to adapt the test experience. It is less suitable for teams that need one framework across several programming languages or cannot meet QUnit 3 ESM's runtime and browser minimums.
Pros and cons
Pros
- Useful browser diagnostics: Failure reports can include expected and actual values, assertion details, and stack traces, making browser failures easier to investigate.
- Isolated DOM tests: Fixture markup resets after each test, helping prevent one test's DOM changes from affecting another.
- Several JavaScript runtimes: Browser, Node.js, SpiderMonkey, and Web Worker support suits codebases that cross those environments.
- Adaptable tooling: Custom assertions, runners, reporters, and plugins let teams shape the framework around their workflow.
- No purchase barrier: The free plan and distribution through standard package channels make it accessible for projects of any size.
Cons
- JavaScript only: Teams seeking a common testing framework for other languages will need a different tool.
- Version requirements matter: QUnit 3's ESM version requires Node.js 18+ and specified minimum browser versions, which may not fit older environments.
- Volunteer-led project work: The team says development is done by volunteers, a factor organizations may weigh when choosing a framework for long-term reliance.
Alternatives
For another JavaScript testing framework, compare Vitest, which is free and open source, with no plan limits stated. Choose Pest instead when you need a PHP testing framework; Pest 5 requires PHP 8.4 or later. ScalaTest is a free, open-source option for Scala testing. Kotest may suit Kotlin projects that want its framework, assertions library, and property testing as independently usable projects.
Hypothesis, NUnit, PHPUnit, and ScalaCheck are additional alternatives to compare. Browse JavaScript Testing Frameworks or Unit Testing Frameworks for more options.
Verdict
Choose QUnit if you need a free JavaScript framework that runs across browsers and server-side environments, with fixture isolation and actionable browser failure reports. Its extensibility and range of runtimes are strong reasons to use it for focused JavaScript testing. Look elsewhere if you need multi-language coverage or QUnit 3's ESM compatibility requirements do not fit your runtimes.
The verdict
QUnit offers a free way to test JavaScript across several runtime environments, with browser reporting and extension options. Check the ESM compatibility requirements for the environments you use.
Questions people ask
Does QUnit have a free plan?
Yes. QUnit is free, and its listed plan costs nothing.
Which environments can run QUnit?
QUnit can run in web browsers, Node.js, SpiderMonkey, and Web Worker threads.
How can I install QUnit 3.0?
It is distributed through the jQuery CDN and npm, and can also be installed with Yarn.
Which browser automation tools integrate with QUnit?
Listed integrations include Karma, Web Test Runner, Testem, and WebdriverIO’s QUnit service.
What compatibility does the ESM version list?
It lists Node.js 18+ and Chrome 61+, Firefox 60+, and Safari 10.1+.
Where can I get help with QUnit?
The project directs users to GitHub issues, Stack Overflow, and a Matrix chat room.
What the maker publishes
- Browser runner
- The browser runner reports test results and resets fixture markup after each test. source
- Browser setup
- QUnit releases are standalone and have no runtime dependencies when used in a browser. source
- Compatibility
- The compatibility guide lists QUnit 3 support for Node.js 18+ and browser versions including Chrome 61+, Firefox 60+, and Safari 10.1+ for its ESM version. source
- Compatibility limit
- The compatibility guide lists Node.js 18+ for QUnit 3’s ESM version. source
- Debugging
- The browser runner can prioritize previously failing tests and rerun selected tests or modules. source
- Distribution
- QUnit 3.0 is distributed through the jQuery CDN and npm, and can also be installed with Yarn. source
- Distribution
- QUnit 3.0.0 is available as JavaScript and CSS files from the jQuery CDN and as an npm package. source
- DOM fixtures
- QUnit resets fixture markup after each test to keep DOM tests isolated. source
- Environments
- QUnit can run in web browsers, Node.js, SpiderMonkey, and Web Workers. source
- Extensibility
- Its APIs support custom assertions, test runners, and reporters. source
- Extensions
- QUnit plugins can extend or modify the framework and developer experience; listed examples include DOM assertions, themes, and JUnit XML reporters. source
- Founded
- 2008 source
- Integrations
- Listed browser automation integrations include Karma, Web Test Runner, Testem, and WebdriverIO’s QUnit service. source
- Integrations
- Documented browser automation integrations include Karma, Web Test Runner, Testem, WebdriverIO, and TestCafe. source
- Intended users
- QUnit is intended for developers testing JavaScript in the environment where the code runs, including browsers, workers, and servers. source
- Maintainers
- The QUnit team says project work is done by volunteers. source
- Offline use
- The project recommends installing or downloading QUnit within the project for local or offline development. source
- Project staffing
- The QUnit team says project work is done by volunteers. source
- Purpose
- QUnit is a JavaScript testing framework originally developed for the jQuery project. source
- Purpose
- QUnit is a JavaScript testing framework originally developed for jQuery and now used by JavaScript libraries and applications. source
- Runtime environments
- QUnit can run in web browsers, Node.js, SpiderMonkey, and Web Worker threads. source
- Security and compliance
- The official pages reviewed do not state security certifications or compliance claims. source
- Setup
- The project describes QUnit as requiring zero configuration for Node.js projects and minimal setup for browser projects. source
- Support
- The project directs users to GitHub issues, Stack Overflow, and a Matrix chat room for help. source
Checked against the maker's pages on 5 Oct 2026.