Need advice about which tool to choose?Ask the StackShare community!
Azure DevOps vs Codecov: What are the differences?
What is 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.
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.
Azure DevOps can be classified as a tool in the "Project Management" category, while Codecov is grouped under "Code Coverage".
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, Codecov provides the following key features:
- Beautiful Reports
- Pull Request Comments
- Interactive Commit Graphs
"Complete and powerful" is the top reason why over 11 developers like Azure DevOps, while over 14 developers mention "More stable than coveralls" as the leading cause for choosing Codecov.
According to the StackShare community, Azure DevOps has a broader approval, being mentioned in 79 company stacks & 68 developers stacks; compared to Codecov, which is listed in 49 company stacks and 29 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.
Pros of Azure DevOps
- Complete and powerful56
- Huge extension ecosystem32
- Azure integration27
- Flexible and powerful26
- One Stop Shop For Build server, Project Mgt, CDCI26
- Everything I need. Simple and intuitive UI15
- Support Open Source13
- Integrations8
- GitHub Integration7
- Cost free for Stakeholders6
- One 4 all6
- Crap6
- Project Mgmt Features6
- Runs in the cloud5
- Agent On-Premise(Linux - Windows)3
- Aws integration2
- Link Test Cases to Stories2
- Jenkins Integration2
- GCP Integration1
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
Sign up to add or upvote prosMake informed product decisions
Cons of Azure DevOps
- Still dependant on C# for agents8
- Half Baked5
- Many in devops disregard MS altogether5
- Not a requirements management tool4
- Jack of all trades, master of none4
- Capacity across cross functional teams not visibile4
- Poor Jenkins integration3
- Tedious for test plan/case creation2
- Switching accounts is impossible1
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