Compare the Top Code Coverage Tools that integrate with Rust as of June 2025

This a list of Code Coverage tools that integrate with Rust. Use the filters on the left to add additional filters for products that have integrations with Rust. View the products that work with Rust in the table below.

What are Code Coverage Tools for Rust?

Code coverage tools are software utilities designed to analyze the source code of an application and report on the level of code that is tested by automated tests. They usually measure the percentage of lines, blocks, or branches of code that have been executed in a test suite. Many popular programming languages have their own code coverage tools available for developers to use. Compare and read user reviews of the best Code Coverage tools for Rust currently available using the table below. This list is updated regularly.

  • 1
    Codecov

    Codecov

    Codecov

    Develop healthier code. Improve your code review workflow and quality. Codecov provides highly integrated tools to group, merge, archive, and compare coverage reports. Free for open source. Plans starting at $10/user per month. Ruby, Python, C++, Javascript, and more. Plug and play into any CI product and workflow. No setup required. Automatic report merging for all CI and languages into a single report. Get custom statuses on any group of coverage metrics. Review coverage reports by project, folder and type test (unit tests vs integration tests). Detailed report commented directly into your pull request. Codecov is SOC 2 Type II certified, which means a third-party audits and attests to our practices to secure our systems and your data.
    Starting Price: $10 per user per month
  • 2
    DeepSource

    DeepSource

    DeepSource

    DeepSource helps you automatically find and fix issues in your code during code reviews, such as bug risks, anti-patterns, performance issues, and security flaws. It takes less than 5 minutes to set up with your Bitbucket, GitHub, or GitLab account. It works for Python, Go, Ruby, and JavaScript. DeepSource covers all major programming languages, Infrastructure-as-Code, secrets detection, code coverage, and more. You won't need any other tool to protect your code. Start building with the most sophisticated static analysis platform for your workflow and prevent bugs before they end up in production. Largest collection of static analysis rules in the industry. Your team's central hub to track and take action on code health. Put code formatting on autopilot. Never let your CI break on style violations. Automatically generates and applies fixes for issues in a couple of clicks.
    Starting Price: $12 per user per month
  • 3
    Tarpaulin

    Tarpaulin

    Tarpaulin

    Tarpaulin is a code coverage reporting tool for the cargo build system, named for a waterproof cloth used to cover cargo on a ship. Currently, tarpaulin provides working line coverage and while fairly reliable may still contain minor inaccuracies in the results. A lot of work has been done to get it working on a wide range of projects, but often unique combinations of packages and build features can cause issues so please report anything you find that's wrong. Also, check out our roadmap for planned features. On Linux Tarpaulin's default tracing backend is still Ptrace and will only work on x86 and x64 processors. This can be changed to the llvm coverage instrumentation with engine llvm, for Mac and Windows this is the default collection method. It can also be run in Docker, which is useful for when you don't use Linux but want to run it locally.
    Starting Price: Free
  • 4
    grcov

    grcov

    grcov

    grcov collects and aggregates code coverage information for multiple source files. grcov processes .profraw and .gcda files which can be generated from llvm/clang or gcc. grcov also processes lcov files (for JS coverage) and JaCoCo files (for Java coverage). Linux, macOS and Windows are supported.
    Starting Price: Free
  • 5
    kcov

    kcov

    kcov

    Kcov is a FreeBSD/Linux/OSX code coverage tester for compiled languages, Python and Bash. Kcov was originally a fork of Bcov, but has since evolved to support a large feature set in addition to that of Bcov. Kcov, like Bcov, uses DWARF debugging information for compiled programs to make it possible to collect coverage information without special compiler switches.
    Starting Price: Free
  • Previous
  • You're on page 1
  • Next