Alternatives to Codecov logo

Alternatives to Codecov

Code Climate, Coveralls, SonarQube, Codacy, and JaCoCo are the most popular alternatives and competitors to Codecov.
387
253
+ 1
89

What is Codecov and what are its top alternatives?

Our patrons rave about our elegant coverage reports, integrated pull request comments, interactive commit graphs, our Chrome plugin and security.
Codecov is a tool in the Code Coverage category of a tech stack.

Top Alternatives to Codecov

  • Code Climate

    Code Climate

    After each Git push, Code Climate analyzes your code for complexity, duplication, and common smells to determine changes in quality and surface technical debt hotspots. ...

  • Coveralls

    Coveralls

    Coveralls works with your CI server and sifts through your coverage data to find issues you didn't even know you had before they become a problem. Free for open source, pro accounts for private repos, instant sign up with GitHub OAuth. ...

  • SonarQube

    SonarQube

    SonarQube provides an overview of the overall health of your source code and even more importantly, it highlights issues found on new code. With a Quality Gate set on your project, you will simply fix the Leak and start mechanically improving. ...

  • Codacy

    Codacy

    Codacy automates code reviews to improve and standardize code quality across large enterprises. It identifies issues through static code analysis. Integrates with GitLab, GitHub & Bitbucket. ...

  • JaCoCo

    JaCoCo

    It is a free code coverage library for Java, which has been created based on the lessons learned from using and integration existing libraries for many years. ...

  • Istanbul

    Istanbul

    It is a JS code coverage tool that computes statement, line, function and branch coverage with module loader hooks to transparently add coverage when running tests. Supports all JS coverage use cases including unit tests, server side functional tests and browser tests. Built for scale. ...

  • uberalls

    uberalls

    Code coverage metric storage service. Provide coverage metrics on differentials with Phabricator and Jenkins, just like Coveralls does for GitHub and TravisCI. ...

Codecov alternatives & related posts

Code Climate logo

Code Climate

488
411
276
Automated Ruby Code Review
488
411
+ 1
276
PROS OF CODE CLIMATE
  • 70
    Auto sync with Github
  • 49
    Simple grade system that motivates to keep code clean
  • 44
    Better coding
  • 29
    Free for open source
  • 21
    Hotspots for quick refactoring candidates
  • 15
    Continued encouragement to a have better / cleaner code
  • 13
    Great UI
  • 11
    Makes you a better coder
  • 10
    Duplication Detection
  • 5
    Safe and Secure
  • 2
    Private
  • 1
    GitHub integration, status inline in PRs
  • 1
    Locally Installable API
  • 1
    Uses rubocop
  • 1
    GitHub only
  • 1
    Extremely accurate in telling you the errors
  • 1
    Python inspection
  • 1
    great open community
CONS OF CODE CLIMATE
  • 1
    Learning curve, static analysis comparable to eslint
  • 1
    Complains about small stylistic decisions

related Code Climate posts

Jerome Dalbert
Senior Backend Engineer at StackShare | 5 upvotes 路 395.9K views

The continuous integration process for our Rails backend app starts by opening a GitHub pull request. This triggers a CircleCI build and some Code Climate checks.

The CircleCI build is a workflow that runs the following jobs:

  • check for security vulnerabilities with Brakeman
  • check code quality with RuboCop
  • run RSpec tests in parallel with the knapsack gem, and output test coverage reports with the simplecov gem
  • upload test coverage to Code Climate

Code Climate checks the following:

  • code quality metrics like code complexity
  • test coverage minimum thresholds

The CircleCI jobs and Code Climate checks above have corresponding GitHub status checks.

Once all the mandatory GitHub checks pass and the code+functionality have been reviewed, developers can merge their pull request into our Git master branch. Code is then ready to deploy!

#ContinuousIntegration

See more
Coveralls logo

Coveralls

391
247
68
Track your project's code coverage over time, changes to files, and badge your GitHub repo
391
247
+ 1
68
PROS OF COVERALLS
  • 45
    Free for public repositories
  • 13
    Code coverage
  • 7
    Ease of integration
  • 2
    More stable than Codecov
  • 1
    Combines coverage from multiple/parallel test runs
CONS OF COVERALLS
    Be the first to leave a con

    related Coveralls posts

    Tim Abbott
    Shared insights
    on
    CodecovCodecovCoverallsCoveralls
    at

    We use Codecov because it's a lot better than Coveralls. Both of them provide the useful feature of having nice web-accessible reports of which files have what level of test coverage (though every coverage tool produces reasonably nice HTML in a directory on the local filesystem), and can report on PRs cases where significant new code was added without test coverage.

    That said, I'm pretty unhappy with both of them for our use case. The fundamental problem with both of them is that they don't handle the ~1% probability situations with missing data due to networking flakiness well. The reason I think our use case is relevant is that we submit coverage data from multiple jobs (one that runs our frontend test suite and another that runs our backend test suite), and the coverage provider is responsible for combining that data together.

    I think the problem is if a test suite runs successfully but due to some operational/networking error between Travis/CircleCI and Codecov the coverage data for part of the codebase doesn't get submitted, Codecov will report a huge coverage drop in a way that is very confusing for our contributors (because they experience it as "why did the coverage drop 12%, all I did was added a test").

    We migrated from Coveralls to Codecov because empirically this sort of breakage happened 10x less on Codecov, but it still happens way more often than I'd like.

    I wish they put more effort in their retry mechanism and/or providing clearer debugging information (E.g. a big "Missing data" banner) so that one didn't need to be specifically told to ignore Codecov/Coveralls when it reports a giant coverage drop.

    See more
    Shared insights
    on
    CodecovCodecovCoverallsCoveralls

    Codecov Although I actually use both codecov and Coveralls, I very much like the graphs I get from codecov, and some of their diagnostic tools.

    See more
    SonarQube logo

    SonarQube

    1K
    1.2K
    29
    Continuous Code Quality
    1K
    1.2K
    + 1
    29
    PROS OF SONARQUBE
    • 16
      Tracks code complexity and smell trends
    • 9
      IDE Integration
    • 4
      Complete code Review
    CONS OF SONARQUBE
    • 4
      Sales process is long and unfriendly
    • 3
      Paid support is poor, techs arrogant and unhelpful

    related SonarQube posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH | 28 upvotes 路 2.2M views

    Our whole DevOps stack consists of the following tools:

    • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
    • Respectively Git as revision control system
    • SourceTree as Git GUI
    • Visual Studio Code as IDE
    • CircleCI for continuous integration (automatize development process)
    • Prettier / TSLint / ESLint as code linter
    • SonarQube as quality gate
    • Docker as container management (incl. Docker Compose for multi-container application management)
    • VirtualBox for operating system simulation tests
    • Kubernetes as cluster management for docker containers
    • Heroku for deploying in test environments
    • nginx as web server (preferably used as facade server in production environment)
    • SSLMate (using OpenSSL) for certificate management
    • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
    • PostgreSQL as preferred database system
    • Redis as preferred in-memory database/store (great for caching)

    The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

    • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
    • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
    • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
    • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
    • Scalability: All-in-one framework for distributed systems.
    • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
    See more
    Ganesa Vijayakumar
    Full Stack Coder | Module Lead | 18 upvotes 路 2M views

    I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

    I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

    As per my work experience and knowledge, I have chosen the followings stacks to this mission.

    UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

    Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

    Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

    Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

    Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

    Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

    Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

    Happy Coding! Suggestions are welcome! :)

    Thanks, Ganesa

    See more
    Codacy logo

    Codacy

    247
    390
    215
    Automate and Standardize Code Reviews for 30+ languages
    247
    390
    + 1
    215
    PROS OF CODACY
    • 39
      Automated code review
    • 33
      Easy setup
    • 26
      Free for open source
    • 18
      Customizable
    • 16
      Helps reduce technical debt
    • 12
      Better coding
    • 12
      Best scala support
    • 10
      Faster Employee Onboarding
    • 9
      Great UI
    • 9
      Duplication detector
    • 8
      PHP integration
    • 5
      Python inspection
    • 4
      Many integrations
    • 3
      Tools for JVM analysis
    • 3
      Github Integration
    • 2
      Must-have for Java
    • 2
      Easy Travis integration
    • 2
      Items can be ignored in the UI
    • 1
      Asdasdas
    • 1
      Gitlab
    • 0
      Asdas
    CONS OF CODACY
    • 5
      No support for private Git or Azure DevOps git

    related Codacy posts

    Ganesa Vijayakumar
    Full Stack Coder | Module Lead | 18 upvotes 路 2M views

    I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

    I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

    As per my work experience and knowledge, I have chosen the followings stacks to this mission.

    UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

    Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

    Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

    Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

    Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

    Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

    Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

    Happy Coding! Suggestions are welcome! :)

    Thanks, Ganesa

    See more

    It is very important to have clean code. To be sure that the code quality is not really bad I use a few tools. I love SonarQube with many relevant hints and deep analysis of code. codebeat isn't so detailed, but it can find complexity issues and duplications. Codacy cannot find more bugs then your IDE. The winner for me is SonarQube that shows me really relevant bugs in my code.

    See more
    JaCoCo logo

    JaCoCo

    56
    47
    0
    A code coverage library for Java
    56
    47
    + 1
    0
    PROS OF JACOCO
      Be the first to leave a pro
      CONS OF JACOCO
        Be the first to leave a con

        related JaCoCo posts

        Istanbul logo

        Istanbul

        36
        5
        0
        A JS code coverage tool written in JS
        36
        5
        + 1
        0
        PROS OF ISTANBUL
          Be the first to leave a pro
          CONS OF ISTANBUL
            Be the first to leave a con

            related Istanbul posts

            uberalls logo

            uberalls

            29
            52
            0
            Track code coverage metrics with Jenkins and Phabricator
            29
            52
            + 1
            0
            PROS OF UBERALLS
              Be the first to leave a pro
              CONS OF UBERALLS
                Be the first to leave a con

                related uberalls posts