QUnit vs Web Test Runner
QUnit
qunitjs.com
Web Test Runner
modern-web.devSide by side
| Figure | QUnit | Web Test Runner |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | 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 | Yes |
| Plans published | 1 | 1 |
| Spec score · JavaScript Testing Frameworks | 8.5 (#2) | 8.2 (#4) |
| Debugging | The browser runner can prioritize previously failing tests and rerun selected tests or modules. | Debug mode opens a real browser window with developer tools. |
| Integrations | Documented browser automation integrations include Karma, Web Test Runner, Testem, WebdriverIO, and TestCafe. | The docs describe using the Playwright launcher with GitHub Actions via Microsoft's Playwright Action. |
| Purpose | QUnit is a JavaScript testing framework originally developed for jQuery and now used by JavaScript libraries and applications. | Web Test Runner is a test runner for web applications. |
| Support | The project directs users to GitHub issues, Stack Overflow, and its Matrix chat room for questions and help. | The project links to Discord for community discussion and lists sponsorship and contributions as ways to support it. |
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.
Web Test Runner
Web Test Runner is a test runner for web applications, installable as an npm development dependency. It runs tests in parallel and isolation, giving each test file its own browser environment. Headless testing is supported through launchers including Puppeteer, Playwright, Selenium, BrowserStack, and WebdriverIO. Playwright can use Chromium, Firefox, and WebKit; BrowserStack runs tests remotely, including against older browser versions. Debug mode opens a browser window with developer tools, and the runner reports browser logs, 404 responses, and errors. Its command line offers interactive watch mode that reruns tests when files change, plus code coverage with configurable thresholds and reports. Default coverage instrumentation uses Chromium. Other features include ES module mocking through import maps and Mocha integration, with guidance for a custom test framework. The project is MIT-licensed, powered by esbuild and Rollup plugins, and directs users to GitHub and Discord for help and discussion. It is free and open source.