Need advice about which tool to choose?Ask the StackShare community!
Codecov vs Jest: What are the differences?
What is Codecov? Hosted coverage reports with awesome features to enhance your CI workflow. Our patrons rave about our elegant coverage reports, integrated pull request comments, interactive commit graphs, our Chrome plugin and security.
What is Jest? Painless JavaScript Unit Testing. Jest provides you with multiple layers on top of Jasmine.
Codecov can be classified as a tool in the "Code Coverage" category, while Jest is grouped under "Javascript Testing Framework".
Some of the features offered by Codecov are:
- Beautiful Reports
- Pull Request Comments
- Interactive Commit Graphs
On the other hand, Jest provides the following key 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
"More stable than coveralls" is the top reason why over 14 developers like Codecov, while over 24 developers mention "Open source" as the leading cause for choosing Jest.
Jest is an open source tool with 26.1K GitHub stars and 3.53K GitHub forks. Here's a link to Jest's open source repository on GitHub.
Repro, Glympse, and Ubiqua are some of the popular companies that use Jest, whereas Codecov is used by Repro, ContentSquare, and homezen. Jest has a broader approval, being mentioned in 263 company stacks & 150 developers stacks; compared to Codecov, which is listed in 49 company stacks and 28 developer stacks.
My website is brand new and one of the few requirements of testings I had to implement was code coverage. Never though it was so hard to implement using a #docker container.
Given my lack of experience, every attempt I tried on making a simple code coverage test using the 4 combinations of #TravisCI, #CircleCi with #Coveralls, #Codecov I failed. The main problem was I was generating the .coverage file within the docker container and couldn't access it with #TravisCi or #CircleCi, every attempt to solve this problem seems to be very hacky and this was not the kind of complexity I want to introduce to my newborn website.
This problem was solved using a specific action for #GitHubActions, it was a 3 line solution I had to put in my github workflow file and I was able to access the .coverage file from my docker container and get the coverage report with #Codecov.
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 Codecov
- More stable than coveralls17
- Easy setup17
- GitHub integration14
- They reply their users11
- Easy setup,great ui10
- Easily see per-commit coverage in GitHub5
- Steve is the man5
- Merges coverage from multiple CI jobs4
- Golang support4
- Free for public repositories3
- Code coverage3
- JSON in web hook3
- Newest Android SDK preinstalled3
- Cool diagrams2
- Bitbucket Integration1
Pros of Jest
- Open source36
- Mock by default makes testing much simpler32
- Testing React Native Apps23
- Parallel test running20
- Fast16
- Bundled with JSDOM to enable DOM testing13
- Mock by default screws up your classes, breaking tests8
- Out of the box code coverage7
- Promise support7
- One stop shop for unit testing6
- Great documentation3
- Assert Library Included2
- Built in watch option with interactive filtering menu1
- Preset support1
- Can be used for BDD0
- Karma0
Sign up to add or upvote prosMake informed product decisions
Cons of Codecov
- GitHub org / team integration is a little too tight1
- Delayed results by hours since recent outage0
- Support does not respond to email0
Cons of Jest
- Documentation4
- Ambiguous configuration4
- Difficult3
- Many bugs still not fixed months/years after reporting2
- Multiple error messages for same error2
- Difficult to run single test/describe/file2
- Ambiguous2
- Bugged2
- BeforeAll timing out makes all passing tests fail1
- Slow1
- Reporter is too general1
- Unstable1
- Bad docs1
- Still does't support .mjs files natively1
- Can't fail beforeAll to abort tests1
- Interaction with watch mode on terminal0
Sign up to add or upvote consMake informed product decisions
What is Codecov?
What is Jest?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Codecov?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Jest?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+17
+32