1.4K
821
+ 1
125

What is Jest?

Jest provides you with multiple layers on top of Jasmine.
Jest is a tool in the Javascript Testing Framework category of a tech stack.
Jest is an open source tool with 28.6K GitHub stars and 4K GitHub forks. Here鈥檚 a link to Jest's open source repository on GitHub

Who uses Jest?

Companies
461 companies reportedly use Jest in their tech stacks, including Airbnb, Facebook, and Instagram.

Developers
906 developers on StackShare have stated that they use Jest.

Jest Integrations

SilverStripe, Wallaby.js, Glamorous, Majestic GUI, and MockIt (open source) are some of the popular tools that integrate with Jest. Here's a list of all 6 tools that integrate with Jest.

Why developers like Jest?

Here鈥檚 a list of reasons why companies and developers use Jest
Jest Reviews

Here are some stack decisions, common use cases and reviews by companies and developers who chose Jest in their tech stack.

Robert Zuber
Robert Zuber
CTO at CircleCI | 16 upvotes 296.4K views
atCircleCICircleCI
Next.js
Next.js
React
React
Storybook
Storybook
TypeScript
TypeScript
Emotion
Emotion
GraphQL
GraphQL
Apollo
Apollo
Jest
Jest
Percy
Percy
Cypress
Cypress

We are in the process of adopting Next.js as our React framework and using Storybook to help build our React components in isolation. This new part of our frontend is written in TypeScript, and we use Emotion for CSS/styling. For delivering data, we use GraphQL and Apollo. Jest, Percy, and Cypress are used for testing.

See more
Eli Hooten
Eli Hooten
CTO at Codecov | 16 upvotes 45.8K views
atCodecovCodecov
Vue.js
Vue.js
Python
Python
vuex
vuex
Jest
Jest

We chose Vue.js at Codecov to replace a front end that was based mostly on server side rendered Python templates, and was getting fairly long in the tooth. The move to Vue.js allowed us to take a more component driven approach to our front end, providing greater flexibility and reuse when creating new pages and refactoring old ones. Another bonus was how easily we could integrate Axios with VueJS for making AJAX calls within Vue.js components and their associated vuex stores. We were also able to easily integrate Vue.js with the Jest testing framework, which allowed to provide test coverage for a front end where none previously existed.

The move to Vue.js has allowed us to be more agile in our front end development by further decoupling our front end from our back end. Additionally, by fully embracing a component-driven approach, we're able to more easily isolate and test functionality, leading to a more readible, maintainable, and extensible front end codebase.

See more
redux-saga
redux-saga
Redux
Redux
React
React
redux-thunk
redux-thunk
Jest
Jest

Choosing redux-saga for my async Redux.js middleware, for a React application, instead of the typical redux-thunk .

Redux-saga is much easier to test than Redux-thunk - it requires no module mocking at all. Converting from redux-thunk to redux-saga is easy enough, as you are only refactoring the action creators - not your redux store or your react components. I've linked a github repo that shows the same solution with both, including Jest tests.

See more
Russel Werner
Russel Werner
Lead Engineer at StackShare | 6 upvotes 60.4K views
atStackShareStackShare
Jest
Jest
Enzyme
Enzyme
React Storybook
React Storybook
Happo.io
Happo.io
Percy
Percy

We use Jest because when we rebooted our "front end" stack earlier last year, we need to have a testing solution (we didn't have any front-end tests before that!). Jest is fast and convenient and it has plenty of community support behind it. It let's us run our unit tests with Enzyme and snapshot tests.

This is an area that we are constantly reviewing to see what can be improved, both in terms of developer needs, accuracy, test maintainability, and coverage.

I'm currently exploring using React Storybook to be the record of snapshot tests and using some online services, such as Happo.io and Percy in our CI pipeline.

See more
Dschinkel Schinkel
Dschinkel Schinkel
Mocha
Mocha
Jest
Jest
JavaScript
JavaScript
React
React
Enzyme
Enzyme
#Tdd
#Bdd
#Testdrivendevelopment

I use both mocha and Jest because:

  • I don't care whether teams use Jest or Mocha. But jest is way too overhyped. Most devs are writing integration tests and think that it's so much better but frankly I don't write integration tests as the way to get both design feedback and confidence when I code. I adhere to the test pyramid, not ice cream cone or the dumb "trophy"

  • I TDD, so I only ever use the "API" of test frameworks. I don't do a lot of integration tests for TDD and all the bells and whistles Jest provides you from the command-line I just don't need. And I certainly do not care about or touch Jest Snapshots, I despise them

  • My tests are fast enough because I write isolated tests with TDD, so I don't run into performance issues. Example: I write my tests in a way that I can run 300 tests in literally 1 second with mocha. So the Jest ability to pinpoint and only run those tests which are affected by code changes. I want to run all of them every time when I TDD. It's a different mindset when you TDD

  • I also mainly code in IntelliJ or WebStorm because I feel the tools in that IDE far surpass VSCode and I also love running the test UI runner in it vs. lousy command-line

  • I feel both mocha and Jest read just fine in terms of code readability. Jest might have shorter assertion syntax but I don't really care. I just care that I can read the damn test and my tests are written well and my test descriptions, as well as the code itself including constants represent business language, not technical. I care most about BDD, clean code, 4 rules of simple design, and SOLID

  • I don't like using mock frameworks so no I don't use Jest's Mocking framework. I don't have to mock a lot in my tests due to the nature of how I strive to code...I keep my design simple and modular using principals such as clean code and 4 rules of simple design. If I must mock, I create very simple custom mocks with JS

  • On the contrary to the belief that integration tests and mount are the way to go (this belief drives me absolutely crazy, especially Dodd's promoting that), I TDD with shallow & enzyme. My tests are simple. My design is driven by my tests and my tests give me quick and useful feedback. I have a course I'm working on coming out soon on TDD with React to show you how to truly test the FE and why the ice cream cone and trophy suck (you're being scammed people). Watch for that here: https://twitter.com/DaveSchinkel/status/1062267649235791873

Don't forget to upvote this post!

Mocha Jest JavaScript React @jsdom Enzyme #tdd #bdd #testdrivendevelopment

See more
Jack Graves
Jack Graves
Head of Product Development at Automation Consultants | 3 upvotes 29.9K views
atAutomation ConsultantsAutomation Consultants
JUnit
JUnit
Jest
Jest
Apache JMeter
Apache JMeter
Mocha
Mocha

We use JUnit and Jest to perform the bulk of our automated test scenarios, with additional work with Apache JMeter for performance testing - for example, the Atlassian Data Center compliance testing is performed with JMeter. Jest provides testing for the React interfaces, which make up the backend of our App offerings. JUnit is used for Unit Testing our Server-based Apps. Mocha is another tool we use.

See more

Jest's Features

  • Familiar Approach: Built on top of the Jasmine test framework, using familiar expect(value).toBe(other) assertions
  • Mock by Default: Automatically mocks CommonJS modules returned by require(), making most existing code testable
  • Short Feedback Loop: DOM APIs are mocked and tests run in parallel via a small node.js command line utility

Jest Alternatives & Comparisons

What are some alternatives to Jest?
Mocha
Mocha is a feature-rich JavaScript test framework running on node.js and the browser, making asynchronous testing simple and fun. Mocha tests run serially, allowing for flexible and accurate reporting, while mapping uncaught exceptions to the correct test cases.
Selenium
Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well.
AVA
Even though JavaScript is single-threaded, IO in Node.js can happen in parallel due to its async nature. AVA takes advantage of this and runs your tests concurrently, which is especially beneficial for IO heavy tests. In addition, test files are run in parallel as separate processes, giving you even better performance and an isolated environment for each test file.
Jasmine
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.
Cypress
Cypress is a front end automated testing application created for the modern web. Cypress is built on a new architecture and runs in the same run-loop as the application being tested. As a result Cypress provides better, faster, and more reliable testing for anything that runs in a browser. Cypress works on any front-end framework or website.
See all alternatives

Jest's Followers
821 developers follow Jest to keep up with related blogs and decisions.
Kaushik Samanta
Grabiel Montero Coello
Lalit Nayyar
Anbuselvan Samiyappan
T瓢 v芒虂n ba虂c si虄
Rahul Singh
Tom Bazarnik
Dylan Nielsen
ozimos
jyjunyz