PC

PHP_CodeCoverage

Free#22 of 27 in Test Coverage Tools

PHP_CodeCoverage: A focused open-source coverage library for PHP and PHPUnit workflows. Ranked #22 of 27 in Test Coverage Tools by our editors (6.9/10); pricing: Open source; best for PHP teams using PHPUnit and Xdebug.

6.9/10★★★☆☆Editor score

Try PHP_CodeCoverage

At a glance

• Editor score
  6.9 / 10
• Pricing
  Open source
• Best for
  PHP teams using PHPUnit and Xdebug
• Paid from
  Free
• Coverage types
  line, branch, path
• Facts checked
  20 Sep 2026

• Where it wins

  • Covers line, branch, and path data through PHP tooling
  • Produces HTML, XML, Clover, Cobertura, and text reports
  • Works with PHPUnit, Xdebug, PCOV, and Composer

• Where it doesn't

  • Supports PHP only
  • Branch and path coverage require Xdebug
  • Requires developer-led integration rather than a hosted interface

Our verdict on PHP_CodeCoverage

PHP_CodeCoverage is an open-source PHP library for collecting, processing, and rendering code coverage information. It suits developers and teams running PHP test suites, particularly PHPUnit-based workflows. The library collects line coverage and can provide branch and path coverage through Xdebug. It also filters included source files, produces coverage summaries, and supports serialized coverage data for workflows that need to store or exchange results.

Its strongest advantage is report and coverage breadth within the PHP ecosystem. Output can be generated as HTML, XML, Clover, OpenClover, Cobertura, Crap4J, or text, while coverage summaries include executable lines, branches, and paths. Composer distribution fits standard PHP package management, and integrations with PHPUnit, Xdebug, and PCOV connect the library to common PHP testing components. Teams that need several report formats for review, tooling, or CI workflows get more flexibility than a line-only reporting utility.

PHP_CodeCoverage is a better fit for teams comfortable assembling developer tooling than for buyers seeking a hosted coverage dashboard or turnkey product. Its scope is limited to PHP, and branch and path coverage depend on Xdebug. Teams that primarily need PHP line coverage, PHPUnit compatibility, filtering, and export options should find its focused library model suitable. Teams working across multiple programming languages, or those looking for a managed interface and broader platform features, should choose a more expansive alternative.

Your product? Our editors can test PHP_CodeCoverage in depth and publish a review, labelled as paid · from $149/mo →

PHP_CodeCoverage pricing

PHP_CodeCoverage fact sheet

PHP_CodeCoverage integrations

PHP_CodeCoverage lists 4 integrations on its own site.

• Composer
• Xdebug
• PCOV
• PHPUnit

Alternatives to PHP_CodeCoverage

• CodecovA broad CI coverage platform with strong pull-request checks, analytics, and integrations.9.4
• CoverallsA mature coverage service for multi-language teams needing CI and pull-request visibility.9.1
• ReportGeneratorA flexible command-line coverage reporter with strong aggregation and history features.8.9

See all PHP_CodeCoverage alternatives →

Used PHP_CodeCoverage? Be the first to review it

The editor score above is our own research. What this page doesn't have yet is a reader's view — what you used PHP_CodeCoverage for, what worked and what didn't. No stars are seeded and no review is paid for; an editor reads every one before it appears.

Write a reviewTwo minutes · verified accounts only · read by an editor before it appears

Website

Reviews come only from verified accounts. Sign in or create an account first — your e-mail is never shown.

Your rating

5 stars★4 stars★3 stars★2 stars★1 star★

Title

Your review

0 characters · at least 80, up to 3,000

Pros (optional · one per line)

Cons (optional · one per line)

Your name (shown with your review)

Role (optional)

Company (optional)

How long have you used it?Prefer not to sayLess than a month1–6 months6–12 months1–2 years2+ years

I've used PHP_CodeCoverage myself and this is my honest opinion — nobody paid or asked me to write it.

Send my reviewPosted from your verified account. Reviews appear after an editor reads them, usually within two working days.

Featured on iTechGuides

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated 7 Oct 2026 · How we research and update