QUnit vs QUnitX
QUnit
qunitjs.comQUnitX
github.comSide by side
| Figure | QUnit | QUnitX |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| iOS | Yes | — |
| Android | Yes | — |
| API | Yes | — |
| Self-hosted | Yes | — |
| Plans published | 1 | 0 |
| Spec score · JavaScript Testing Frameworks | 8.5 (#2) | 7.2 (#17) |
| Browser runner | The browser runner reports test results and resets fixture markup after each test. | The separate qunitx-cli bundles tests for a real browser and streams TAP to the terminal, with an optional live QUnit UI. |
| Integrations | Documented browser automation integrations include Karma, Web Test Runner, Testem, WebdriverIO, and TestCafe. | The README documents installation through npm and Deno, and describes a JSR package published from CI with provenance. |
| Purpose | QUnit is a JavaScript testing framework originally developed for jQuery and now used by JavaScript libraries and applications. | QUnitX lets teams write one JavaScript or TypeScript test file and run it unchanged with Node.js, Deno, or in a browser. |
| Setup | The project describes QUnit as requiring zero configuration for Node.js projects and minimal setup for browser projects. | The project says it needs no configuration, setup files, transform pipeline, injected globals, or runtime dependencies. |
Plans
In their own words
QUnit
QUnit is a free JavaScript testing framework first developed for the jQuery project. It runs in web browsers, Node.js, SpiderMonkey and Web Worker threads, so developers can test code in different runtime environments. Its APIs allow custom assertions, test runners and reporters. Browser releases have no runtime dependencies, and 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. Its browser reporter presents results and can include expected and actual values, assertion details and failure stack traces. Developers can rerun selected tests or modules and prioritize previously failing tests. Guides cover modules, asynchronous tests, callbacks and assertions, while plugins can add or modify capabilities such as DOM assertions, themes and JUnit XML reports. QUnit integrates with browser automation tools including Karma, Web Test Runner, Testem and WebdriverIO’s QUnit service. QUnit 3.0 is distributed through the jQuery CDN and npm, and is also installable with Yarn. For its ESM version, the compatibility guide lists Node.js 18+ and specified browser versions.
QUnitX
QUnitX lets teams write JavaScript or TypeScript tests in one file and run them with Node.js, Deno, or in a browser. The project says it needs no configuration files, transform pipeline, injected globals, or runtime dependencies, and that TypeScript runs as-is. Its assertions cover deep and partial equality, error matching, ordered steps, assertion counts, and per-test timeouts. Tests can be organized in nested modules with before, beforeEach, afterEach, and after hooks. The browser interface filters tests, shares filtered views by URL, reruns individual tests, and displays assertion differences. The linked qunitx-cli runs tests in headless Chromium, Firefox, or WebKit and streams TAP output. It also supports esbuild plugins, GitHub-annotated output, JUnit XML, V8 coverage reports, and a JavaScript API. QUnitX is free and lists an MIT license. The core requires Node.js 22 or later or Deno 2 or later; the CLI requires Node.js 24 or later or Deno 2.7 or later. Its default standalone Chromium mode also needs system Chrome or CHROME_BIN. Browser coverage has a source-map limitation.