# C++ coverage reports for people, CI and AI

- Section: Coverage Reports
- Canonical: https://covdbg.com/coverage-reports/

---

Keep the tools your team already uses. Export coverage for CI, review it in an HTML report, or let an AI agent inspect the results through MCP.

- **For your pipeline: LCOV and Codecov.** Export a familiar format and upload it from CI. Keep coverage visible in the pull request, alongside the review your team already does. See [Codecov](/docs/integrations/codecov.md).
- **For a closer look: portable HTML reports.** The exporter creates a static report you can open locally. Filter files, inspect execution counts, and move between uncovered lines. See [HTML Reports](/docs/guides/html-reports.md).
- **For your coding agent: structured MCP tools.** The server lets your agent run tests under coverage, inspect the gaps in context, and measure again after improving the tests. See [MCP Server](/docs/integrations/mcp.md).

## Export results from your coverage database

Run your existing executable with its PDB, then merge suites when you need a combined view. Export LCOV for CI or keep the database for detailed analysis.

```powershell
covdbg -c .covdbg.yaml -o coverage.covdb tests.exe
covdbg convert -i coverage.covdb -f LCOV -o coverage.lcov
```

Cobertura (`-f COBERTURA`), GCOV and the database itself are compared in [Report Formats](/docs/guides/report-formats.md). For CI, see [GitHub Actions](/docs/integrations/github-actions.md).

## Open and share an HTML report

The HTML exporter writes an overview, source pages, and local assets to one directory. Open `index.html` directly or publish the folder to a static host.

```powershell
covdbg convert -i coverage.covdb -f HTML -o coverage-html
```

Source is read at export time. Use the matching checkout, and remember that the report contains source text when choosing where to share it. See [HTML Reports](/docs/guides/html-reports.md).

To set this up with a coding agent, use the [Quick Start Using AI](/docs/getting-started/ai-quick-start.md).