Skip to content
Go to file

Latest commit

It only passing some of the time on the latest Node 14 build, confirmed
locally on macOS and also seen at Travis CI on Linux.

It appears V8 now realizes destroy() is a no-op and sometimes inlines
the code or otherwise makes it no longer appear in the heap.

Instead of trying to fool V8 with no-op methods in afterEach(), make
explicitly remain in memory using a regular Set, and then clear it
from there when we're ready for it and calling GC.

Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Build Status Coverage Status Chat on Gitter FOSSA Status npm

QUnit - A JavaScript Unit Testing Framework.

QUnit is a powerful, easy-to-use, JavaScript unit testing framework. It's used by the jQuery project to test its code and plugins but is capable of testing any generic JavaScript code (and even capable of testing JavaScript code on the server-side).

QUnit is especially useful for regression testing: Whenever a bug is reported, write a test that asserts the existence of that particular bug. Then fix it and commit both. Every time you work on the code again, run the tests. If the bug comes up again - a regression - you'll spot it immediately and know how to fix it, because you know what code you just changed.

Having good unit test coverage makes safe refactoring easy and cheap. You can run the tests after each small refactoring step and always know what change broke something.

QUnit is similar to other unit testing frameworks like JUnit, but makes use of the features JavaScript provides and helps with testing code in the browser, such as built in support for asynchronicity and exception handling.


If you need help using QUnit, chat with us on Gitter.

To report a bug or request a new feature, open an issue.


If you are interested in helping develop QUnit, check out our contributing guide.

You canā€™t perform that action at this time.