Compare the Top Code Coverage Tools that integrate with Nango as of October 2025

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

What are Code Coverage Tools for Nango?

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 Nango currently available using the table below. This list is updated regularly.

  • 1
    Code Climate

    Code Climate

    Code Climate

    Velocity provides in-depth, contextual analytics that equip engineering leaders to support stuck team members, address team roadblocks, and streamline engineering processes. Actionable metrics for engineering leaders. Velocity turns data from commits and pull requests into the insights you need to make lasting improvements to your team’s productivity. Quality: Automated code review for test coverage, maintainability and more so that you can save time and merge with confidence. Receive automated code review comments on your pull requests. Our 10-point technical debt assessment provides real-time feedback, so you can save time and focus on what matters in your code review discussions. Get test coverage right, every time. See coverage line by line within diffs. Never merge code without sufficient tests again. At a glance, identify frequently changed files that have inadequate coverage and maintainability issues. Track your progress against measurable goals, day-by-day.
  • 2
    Atlassian Clover
    For many years Atlassian Clover has provided Java and Groovy developers a reliable source for code coverage analysis. This dependability has allowed us to focus our development efforts on delivering new features and improvements to our core offerings, including Jira Software, Bitbucket, and others. All of this has lead to our decision to open source Clover, what we believe is the best way to give Clover the focus and attention it deserves. Developers are ready and eager to contribute to Clover as they have with our other open-source projects including the IDE connectors and dozens of libraries. Although Clover is already a powerful code coverage tool we’re excited to see what the community will do to make it thrive.
  • Previous
  • You're on page 1
  • Next