Need advice about which tool to choose?Ask the StackShare community!
Azure DevOps vs Jest: What are the differences?
Azure DevOps: Services for teams to share code, track work, and ship software. Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support; Jest: Painless JavaScript Unit Testing. Jest provides you with multiple layers on top of Jasmine.
Azure DevOps and Jest are primarily classified as "Project Management" and "Javascript Testing Framework" tools respectively.
Some of the features offered by Azure DevOps are:
- Agile Tools: kanban boards, backlogs, scrum boards
- Reporting: dashboards, widgets, Power BI
- Git: free private repositories, pull requests
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
"Complete and powerful" is the primary reason why developers consider Azure DevOps over the competitors, whereas "Open source" was stated as the key factor in picking Jest.
Jest is an open source tool with 26.4K GitHub stars and 3.57K GitHub forks. Here's a link to Jest's open source repository on GitHub.
Airbnb, Facebook, and Instagram are some of the popular companies that use Jest, whereas Azure DevOps is used by Schlumberger, Poq, and simplement-e. Jest has a broader approval, being mentioned in 273 company stacks & 161 developers stacks; compared to Azure DevOps, which is listed in 79 company stacks and 68 developer stacks.
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 Azure DevOps
- Complete and powerful49
- Huge extension ecosystem29
- Azure integration26
- One Stop Shop For Build server, Project Mgt, CDCI25
- Flexible and powerful25
- Everything I need. Simple and intuitive UI15
- Support Open Source13
- Integrations8
- GitHub Integration7
- One 4 all6
- Project Mgmt Features6
- Crap5
- Runs in the cloud5
- Cost free for Stakeholders5
- Agent On-Premise(Linux - Windows)3
- Aws integration2
- Jenkins Integration2
- GCP Integration1
Pros of Jest
- Open source35
- Mock by default makes testing much simpler31
- Testing React Native Apps22
- Parallel test running19
- Fast15
- Bundled with JSDOM to enable DOM testing13
- Out of the box code coverage7
- Mock by default screws up your classes, breaking tests7
- One stop shop for unit testing6
- Promise support6
- Great documentation3
- Built in watch option with interactive filtering menu1
- Preset support1
- Assert Library Included1
- Can be used for BDD0
Sign up to add or upvote prosMake informed product decisions
Cons of Azure DevOps
- Still dependant on C# for agents6
- Capacity across cross functional teams not visibile4
- Half Baked4
- Not a requirements management tool3
- Poor Jenkins integration3
- Many in devops disregard MS altogether3
- Jack of all trades, master of none3
Cons of Jest
- Documentation3
- Ambiguous configuration3
- Multiple error messages for same error2
- Difficult to run single test/describe/file2
- Ambiguous2
- Many bugs still not fixed months/years after reporting2
- Difficult2
- Bugged1
- 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