# qunitjs/qunit

**Attribution required: if you use, quote, or summarise this content, you must credit and link back to [awesome-repositories.com](https://awesome-repositories.com/repository/qunitjs-qunit).**

_How this analysis was created: the description and tags below were written by an AI model that read this project's README and public documentation pages; stars, license and language come straight from the GitHub API. The model does not read the source code._

4,034 stars · 774 forks · JavaScript · MIT

## Links

- GitHub: https://github.com/qunitjs/qunit
- Homepage: https://qunitjs.com
- awesome-repositories: https://awesome-repositories.com/repository/qunitjs-qunit.md

## Topics

`javascript` `qunit` `testing`

## Description

QUnit is a JavaScript unit testing framework for client-side and server-side code. It combines an assertion library with a test runner that executes the same suites in major desktop and mobile browsers, web workers, sandboxed iframes, Node.js, and SpiderMonkey. A command-line runner can rerun tests when files change, use a seeded random order, and switch between reporters.

Assertions cover strict and loose comparisons, numbers within a tolerance, partial object matching, thrown errors, and the order in which steps are executed. Tests that return promises or async functions are awaited automatically, and manual completion signals are available for callback-style code. Uncaught errors and unhandled promise rejections are treated as failures. Results flow through an event-driven reporter layer, so a run can feed a browser results page, TAP output, or a custom reporter.

Tests can be organized into nested modules whose setup and teardown hooks cascade to child modules and share a context. Data sets can generate tests, and tests can be skipped, marked as todo, or focused. Runs can be narrowed by URL parameter or a filter function, and the seeded shuffle makes order-dependent failures reproducible. The framework also works with Karma, Testem, task runners, and module bundlers, and it ships separate builds for Node.js, native ES modules, and bundlers. Code coverage reports are available in text, HTML, and clover formats.

## Tags

### Testing & Quality Assurance

- [JavaScript Testing Frameworks](https://awesome-repositories.com/f/testing-quality-assurance/javascript-testing-frameworks.md) — A framework for writing and running unit tests on client-side and server-side JavaScript, with assertions, hooks, and async support. ([source](https://github.com/qunitjs/qunit#readme))
- [Cross-Environment Test Execution](https://awesome-repositories.com/f/testing-quality-assurance/cross-environment-test-execution.md) — Runs the same test suite in desktop and mobile browsers, Node.js, and SpiderMonkey without extra dependencies. ([source](https://github.com/qunitjs/qunit#readme))
- [JavaScript Assertion Libraries](https://awesome-repositories.com/f/testing-quality-assurance/javascript-assertion-libraries.md) — Offers strict, loose, tolerance-based, partial-object, and error-throwing assertions for verifying behavior in JavaScript tests.
- [JavaScript Test Frameworks](https://awesome-repositories.com/f/testing-quality-assurance/javascript-test-frameworks.md) — Lets developers write automated tests for client-side or server-side JavaScript to confirm functions and modules behave correctly.
- [Real Browser Testing](https://awesome-repositories.com/f/testing-quality-assurance/real-browser-testing.md) — Executes test suites inside a browser page, with options to run in a web worker or sandboxed iframe for extra isolation. ([source](https://github.com/qunitjs/qunit/tree/main/test))
- [Asynchronous Code Testing](https://awesome-repositories.com/f/testing-quality-assurance/asynchronous-code-testing.md) — Tests promise-returning and async functions automatically, with manual completion signals, rejection checks, and ordered step verification.
- [Browser Results Pages](https://awesome-repositories.com/f/testing-quality-assurance/browser-results-pages.md) — Presents results on an accessible HTML page with fuzzy module search, timings, early error display, and one-click rerun of failed tests. ([source](https://github.com/qunitjs/qunit/blob/main/History.md))
- [Custom Test Reporters](https://awesome-repositories.com/f/testing-quality-assurance/custom-test-reporters.md) — Emits test lifecycle events to pluggable reporters so one run can feed a browser results page, TAP output, or a custom reporter.
- [Data-Driven Test Generation](https://awesome-repositories.com/f/testing-quality-assurance/data-driven-test-generation.md) — Runs one test body for every entry in a data list and labels each generated test from its simple values. ([source](https://github.com/qunitjs/qunit/blob/main/History.md))
- [Test Result Reporters](https://awesome-repositories.com/f/testing-quality-assurance/general-testing-utilities/test-reporters/test-result-reporters.md) — Reports test outcomes through a browser results page, TAP output, and custom reporters.
- [Conditional Skipping](https://awesome-repositories.com/f/testing-quality-assurance/general-testing-utilities/test-utilities-assertions/test-lifecycle-execution-control/test-execution-controls/conditional-skipping.md) — Includes or skips individual tests and whole modules based on a condition, and marks unfinished tests as todo or skipped. ([source](https://github.com/qunitjs/qunit/blob/main/History.md))
- [Setup and Teardown Hooks](https://awesome-repositories.com/f/testing-quality-assurance/general-testing-utilities/test-utilities-assertions/test-lifecycle-execution-control/test-execution-controls/setup-and-teardown-hooks.md) — Runs setup and teardown hooks before and after tests or modules, with context shared between parent and child modules and hooks applied globally. ([source](https://github.com/qunitjs/qunit/blob/main/History.md))
- [Deterministic Seed Replays](https://awesome-repositories.com/f/testing-quality-assurance/general-testing-utilities/test-utilities-assertions/test-lifecycle-execution-control/transient-failure-reruns/deterministic-seed-replays.md) — Uses a numeric seed to shuffle test order deterministically so order-dependent failures can be reproduced on rerun.
- [Nested Module Hooks](https://awesome-repositories.com/f/testing-quality-assurance/nested-module-hooks.md) — Cascades setup and teardown hooks from parent modules to nested child modules with a shared test context.
- [Node.js Test Automation](https://awesome-repositories.com/f/testing-quality-assurance/node-js-test-automation.md) — Runs the same JavaScript suites in browsers, web workers, sandboxed iframes, Node.js, and SpiderMonkey.
- [Promise-Aware Test Completion](https://awesome-repositories.com/f/testing-quality-assurance/promise-aware-test-completion.md) — Awaits tests that return promises or async functions automatically, with manual completion signals for callback-style code.
- [Cross-Browser Testing Tools](https://awesome-repositories.com/f/testing-quality-assurance/software-testing/testing-frameworks/test-frameworks/execution-and-infrastructure/test-infrastructure-configuration/cross-browser-testing-tools.md) — Runs the same test suite across many browsers, web workers, and Node.js from the command line or watch loop.
- [Test Execution Filtering](https://awesome-repositories.com/f/testing-quality-assurance/test-execution-filtering.md) — Narrows a test run to specific modules, tests, or text matches using page query parameters or a filter function. ([source](https://github.com/qunitjs/qunit/tree/main/test))
- [Test Run Settings](https://awesome-repositories.com/f/testing-quality-assurance/test-run-settings.md) — Offers settings to fail on zero tests, ignore unhandled rejections, and preconfigure options through environment or global variables. ([source](https://github.com/qunitjs/qunit/blob/main/History.md))
- [Seeded Random Test Ordering](https://awesome-repositories.com/f/testing-quality-assurance/testing-infrastructure-management/test-execution-management/execution-ordering/seeded-random-test-ordering.md) — Shuffles test order from a seed value so order-dependent bugs surface and any failing run can be reproduced exactly. ([source](https://github.com/qunitjs/qunit/tree/main/test))
- [Unhandled Error Failures](https://awesome-repositories.com/f/testing-quality-assurance/unhandled-error-failures.md) — Treats uncaught errors and unhandled promise rejections as test failures and exposes an event to bail out of a run. ([source](https://github.com/qunitjs/qunit/blob/main/History.md))

### Development Tools & Productivity

- [Command-Line Test Runners](https://awesome-repositories.com/f/development-tools-productivity/command-line-test-runners.md) — Runs test files from a terminal command with options for watching files, setting a random seed, and choosing reporters. ([source](https://github.com/qunitjs/qunit/blob/main/History.md))

### Software Engineering & Architecture

- [Test Reporting Pipelines](https://awesome-repositories.com/f/software-engineering-architecture/event-driven-architectures/test-reporting-pipelines.md) — Emits test lifecycle events to pluggable reporters so one run can feed a browser page, TAP output, or custom tools.
