Need advice about which tool to choose?Ask the StackShare community!
Codecov vs Codefresh: 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 Codefresh? CI/CD Tailor-Made For Docker. Automate and parallelize testing. Codefresh allows teams to spin up on-demand compositions to run unit and integration tests as part of the continuous integration process. Jenkins integration allows more complex pipelines.
Codecov can be classified as a tool in the "Code Coverage" category, while Codefresh is grouped under "Container Tools".
Some of the features offered by Codecov are:
- Beautiful Reports
- Pull Request Comments
- Interactive Commit Graphs
On the other hand, Codefresh provides the following key features:
- Instant Dev, test and feature preview environments: Enables all team members to run any image as a standalone or composition for feature preview, manual testing, bug reproduction and more. Collaborate on features before pushing them into staging and production.
- Testing with every step: Configure your pipeline to run integration and unit tests with every step
- Instantly test all code changes in the Codefresh build system before pushing to staging & production. Run integration, unit tests in parallel.
"More stable than coveralls" is the top reason why over 14 developers like Codecov, while over 6 developers mention "Fastest and easiest way to work with Docker" as the leading cause for choosing Codefresh.
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 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 Codefresh
- Fastest and easiest way to work with Docker11
- Great support/fast builds/awesome ui7
- Great onboarding6
- Freestyle build steps to support custom CI/CD scripting5
- Robust feature-preview/qa environments on-demand4
- Easy setup4
- Kubernetes Integration2
- Codefresh Runner for supporting hybrid infra2
- GitOps friendly2
- Firendly API2
- Slack Integration2
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 Codefresh
- Questionable product quality and stability1
- Expensive compared to alternatives1