# covdbg: C++ Code Coverage for Windows and AI Workflows - Section: Home - Canonical: https://covdbg.com/ --- New in 1.5.1: see the [covdbg 1.5.1 announcement](/announcing-covdbg-1-5-1.md). **See which C++ code your tests cover.** covdbg is C++ code coverage for Windows. It measures the binary you already build, with its PDB, for developers and AI agents. No rebuild required. - [Quick start using AI](/docs/getting-started/ai-quick-start.md) - [Download for Windows](/download.md) Free for open source and personal use. There is no license key; [you sign in once](/pricing.md). Current version: 1.5.1. See also the [documentation](/docs.md). ## Coverage for your AI agent covdbg's built-in MCP server lets your coding agent run coverage, find untested paths, and read the surrounding source. The agent can add a focused test, run it, and check whether it exercised the gap. The same measurements work for you in the editor, in an HTML report, and in CI. 1. **Measure:** run your real tests. 2. **Inspect:** find uncovered paths. 3. **Improve:** add tests, and measure again. See [MCP Server](/docs/integrations/mcp.md), [HTML reports](/docs/guides/html-reports.md) and [Codecov](/docs/integrations/codecov.md). ## Get started 1. **Run.** Works with any Windows x64, ARM64 or 32-bit x86 binary that has a PDB: tests, services, or the application itself. ```powershell covdbg -c .covdbg.yaml -o coverage.covdb tests.exe ``` 2. **Merge.** Combine unit tests, integration runs, and a baseline of the whole application into one database. ```powershell covdbg merge -i unit.covdb -i integration.covdb -o all.covdb ``` 3. **Export.** Write Cobertura, LCOV, GCOV or HTML. Keep your existing quality gates and share a source-level report. ```powershell covdbg convert -i all.covdb -f LCOV -o coverage.lcov ``` ## No rebuild covdbg works like a debugger. It starts your executable, reads the PDB, and places lightweight probes while the program runs. Your build stays as it is, with the same compiler, the same flags, and the same binary you ship. - MSVC and any toolchain that produces PDBs, C++23 included - Follows child processes and DLLs, and works with long-running services - Choose which files and functions to track in a small YAML file See the [Quick Start Guide](/docs/getting-started/quick-start.md) and the [Configuration Reference](/docs/reference/configuration.md). ## In your editor The [VS Code extension](/docs/integrations/vscode.md) runs your tests under covdbg from the Test Explorer and marks each line in the gutter: green for lines that ran, red for lines that did not. Run one test or the whole suite, see per-file percentages refreshed on every run, and get the same numbers as the CLI, because it uses the same database. A [CLion plugin](/docs/integrations/clion.md) is available too. ## In your pipeline Add covdbg to GitHub Actions, Azure DevOps, or Jenkins, convert the result to LCOV or Cobertura, and upload it to Codecov or your own quality gate. A public repository on GitHub Actions [needs no token at all](/docs/integrations/github-actions.md#a-public-repository-needs-no-secret): grant the job `id-token: write`. Elsewhere a project token covers every author with a seat, so nobody has to sign in on a build agent. - First-class GitHub Action: `liasoft/setup-covdbg` - Baseline coverage reports code that is not linked into a test as uncovered instead of leaving it out - Merge parallel jobs into one report See [GitHub Actions](/docs/integrations/github-actions.md) and [Codecov](/docs/integrations/codecov.md). ## Plans - **Free, $0:** for personal use and open source. Unlimited public repositories, and one private repository at a time that you can switch at any time. CLI, VS Code, and public CI, with no secret on GitHub Actions. Cobertura, LCOV and GCOV export. Your own dashboard at app.covdbg.com. - **Team, $12 per user per month:** all repositories and CI. Unlimited private repositories with no lock, CI project tokens that cover all seated authors, and priority support. Seats are bought at https://app.covdbg.com/pricing; cancel any time. - **Enterprise:** volume pricing, purchase orders and annual invoicing. [Request a quote](/pricing/request-quote.md). See [Pricing](/pricing.md) for how licensing works. ## Frequently asked questions **Do I need to recompile my code?** No. covdbg works with your existing binaries. Point it at an .exe or .dll built with debug symbols (PDB) and it handles the instrumentation at runtime. No compiler flags, no build system changes. **Which compilers are supported?** MSVC, and any compiler that produces Windows x64, ARM64 or 32-bit x86 binaries with PDB debug information. Modern language features up to C++23 are fully supported. **How much does covdbg cost?** It is free for open source and for personal use on one private repository. Teams pay $12 per user per month at app.covdbg.com. **Is there a license key?** No. You sign in once per machine with `covdbg login`; in CI, a project token takes the place of the sign-in, and a public repository on GitHub Actions needs none: covdbg presents the job's own GitHub workflow token. The license service checks each run, and the result is cached so covdbg keeps working offline for a few weeks. **What does covdbg send to the license service?** The repository's git remote URL, the email address in your git configuration, and your sign-in, project token, or the job's GitHub workflow token. After a run, one optional telemetry event with the covdbg version, the Windows version, run time, and exit code. Never source code, file names, or coverage data. [Data and Telemetry](/docs/reference/data-and-telemetry.md) lists every field.