Need advice about which tool to choose?Ask the StackShare community!
Jest vs QUnit: What are the differences?
Developers describe Jest as "Painless JavaScript Unit Testing". Jest provides you with multiple layers on top of Jasmine. On the other hand, QUnit is detailed as "A JavaScript Unit Testing framework". QUnit is a powerful, easy-to-use JavaScript unit testing framework. It's used by the jQuery, jQuery UI and jQuery Mobile projects and is capable of testing any generic JavaScript code, including itself!.
Jest and QUnit can be categorized as "Javascript Testing Framework" tools.
"Open source" is the primary reason why developers consider Jest over the competitors, whereas "Simple" was stated as the key factor in picking QUnit.
Jest and QUnit are both open source tools. It seems that Jest with 26.3K GitHub stars and 3.57K forks on GitHub has more adoption than QUnit with 3.83K GitHub stars and 763 GitHub forks.
Airbnb, Facebook, and Instagram are some of the popular companies that use Jest, whereas QUnit is used by Square, Convertale, and ALV CH. Jest has a broader approval, being mentioned in 271 company stacks & 161 developers stacks; compared to QUnit, which is listed in 11 company stacks and 6 developer stacks.
We were able to combine multiple tools with Jest and React Testing Library (e.g. sinon, enzyme, chai). Jest has powerful cli options and increased performance including from parallel testing processes. Migrating was reasonably straight forward as there is a code transformation script to do most of the leg work. Jest's documentation is excellent.
As we all know testing is an important part of any application. To assist with our testing we are going to use both Cypress and Jest. We feel these tools complement each other and will help us get good coverage of our code. We will use Cypress for our end to end testing as we've found it quite user friendly. Jest will be used for our unit tests because we've seen how many larger companies use it with great success.
Postman will be used to do integration testing with the backend API we create. It offers a clean interface to create many requests, and you can even organize these requests into collections. It helps to test the backend API first to make sure it's working before using it in the front-end. Jest can also be used for testing and is already embedded into React. Not only does it offer unit testing support in javascript, it can also do snapshot testing for the front-end to make sure components are rendering correctly. Enzyme is complementary to Jest and offers more functions such as shallow rendering. UnitTest will be used for Python testing as it is simple, has a lot of functionality and already built in with python. Sentry will be used for keeping track of errors as it is also easily integratable with Heroku because they offer it as an add-on. LogDNA will be used for tracking logs which are not errors and is also a Heroku add-on. Its good to have a separate service to record logs, monitor, track and even fix errors in real-time so our application can run more smoothly.
Pros of Jest
- Open source35
- Mock by default makes testing much simpler31
- Testing React Native Apps23
- Parallel test running19
- Fast15
- Bundled with JSDOM to enable DOM testing13
- Mock by default screws up your classes, breaking tests8
- Out of the box code coverage7
- Promise support6
- One stop shop for unit testing6
- Great documentation3
- Assert Library Included2
- Built in watch option with interactive filtering menu1
- Preset support1
- Karma0
- Can be used for BDD0
Pros of QUnit
- Simple6
- Open Source4
- Promise support3
- Easy setup3
- Excellent GUI1
Sign up to add or upvote prosMake informed product decisions
Cons of Jest
- Ambiguous configuration3
- Difficult3
- Documentation3
- Many bugs still not fixed months/years after reporting2
- Multiple error messages for same error2
- Difficult to run single test/describe/file2
- Ambiguous2
- Bugged2
- Slow1
- Reporter is too general1
- BeforeAll timing out makes all passing tests fail1
- Unstable1
- Bad docs1
- Still does't support .mjs files natively1
- Can't fail beforeAll to abort tests1
- Interaction with watch mode on terminal0