Getting Started

Code Coverage with Qlty

Code coverage is used in software development to measure the percentage of code lines, branches, or paths that are executed during code exercises, such as automated tests. The primary goal of measuring code coverage is to identify areas of a program that are not adequately exercised, allowing developers to write additional tests to increase coverage and improve the overall reliability and quality of the software.

Code coverage reporting is part of Qlty Cloud.

Why use Qlty for code coverage?

Qlty’s code coverage integration is a workflow and visualization platform for improving code coverage across your projects. It integrates seamlessly with your existing coverage tools, enhancing your development process with configurable pull request gates, team-level metrics, and trend analysis that helps engineers work toward common coverage goals while highlighting overall progress across your codebase.

Advantages

Consolidated metrics dashboard with coverage data correlated against other code quality metrics.

Unified source view with toggleable overlays for coverage data and static analysis findings.

Configurable PR gates for ensuring new code meets your team’s code coverage standards, and/or that your total coverage remains above a defined threshold.

Our platform ingests coverage reports from any source via standardized formats, supporting all major languages and frameworks through a language-agnostic architecture. Setup is minimal, requiring only the integration of our coverage uploader into your existing CI pipeline after your test coverage generation step.

Advanced Features

  • Delta Analysis: Intelligent measurement of coverage changes in modified code, prioritizing new code coverage
  • Coverage Isolation: Segment coverage metrics by test type (unit, integration, e2e) for targeted improvement
  • Selective Testing: Support for workflows which do not run the whole test suite on every commit
  • Server Side and Client Side Merging: Able to merge coverage reports on the same machine or across multiple isolated machines using both client and/or server side merging

Implementation Path