Need advice about which tool to choose?Ask the StackShare community!
Jasmine vs Jest: What are the differences?
What is Jasmine? DOM-less simple JavaScript testing framework. Jasmine is a Behavior Driven Development testing framework for JavaScript. It does not rely on browsers, DOM, or any JavaScript framework. Thus it's suited for websites, Node.js projects, or anywhere that JavaScript can run.
What is Jest? Painless JavaScript Unit Testing. Jest provides you with multiple layers on top of Jasmine.
Jasmine and Jest can be categorized as "Javascript Testing Framework" tools.
"Can also be used for tdd " is the primary reason why developers consider Jasmine over the competitors, whereas "Open source" was stated as the key factor in picking Jest.
Jasmine and Jest are both open source tools. It seems that Jest with 26.1K GitHub stars and 3.53K forks on GitHub has more adoption than Jasmine with 14.4K GitHub stars and 2.12K GitHub forks.
Repro, Glympse, and Ubiqua are some of the popular companies that use Jest, whereas Jasmine is used by Coderus, Infoshare, and Ztory. Jest has a broader approval, being mentioned in 262 company stacks & 150 developers stacks; compared to Jasmine, which is listed in 143 company stacks and 75 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.
We use Mocha for our FDA verification testing. It's integrated into Meteor, our upstream web application framework. We like how battle tested it is, its' syntax, its' options of reporters, and countless other features. Most everybody can agree on mocha, and that gets us half-way through our FDA verification and validation (V&V) testing strategy.