Search results for "{{ search.query }}"

No results found for "{{search.query}}". 
View All Results

Setting Up Test Coverage

Adding test coverage reporting really completes the picture of your codebase’s health by displaying your test coverage data in the context of your static analysis results. In our previous article, we saw how our GitHub browser extension allows you to view coverage line-by-line. Once you’ve set up test coverage reporting you can also:

  • view test coverage reports for each file alongside quality metrics like complexity, duplication, and churn,

  • toggle between viewing code issues and test coverage line-by-line in the same source listings,

  • block PRs from being merged if they don't meet your team's standards for test coverage percentage.

We accept test coverage data from virtually any location, including locally run tests or your continuous integration (CI) service, and we support a variety of programming languages and test coverage formats, including Ruby, JavaScript, Go, Python, PHP, Java, and more.

For additional details about setting up test coverage, see our Test Coverage Reporter documentation.

Now that you’ve customized your analysis and got a clear picture of the health of your repo, it’s time to let your team in on the action. Next up, we'll look at best practices for rolling Code Climate out to your team.

Setting Up Test Coverage