codeclimate/php-test-reporter
PHP Test Reporter submits PHPUnit/PHPSpec code coverage to Code Climate. Generates coverage in CI and posts results to your Code Climate repo, helping track test quality over time. Simple CLI setup for common PHP workflows.
This package supports integrating PHP test coverage into Code Climate for trend tracking and quality gate enforcement, eliminating manual reporting efforts. It validates a "buy" decision over building custom tooling, as it provides pre-built CI/CD integration with minimal configuration. Key use cases include teams needing automated coverage reporting for legacy PHP projects, enforcing coverage thresholds across builds, and centralizing quality metrics alongside Code Climate’s static analysis—especially where existing CI pipelines already use PHPUnit and Clover format outputs.
Consider this package only if your project uses Code Climate, relies on PHPUnit Clover reports, and operates in a stable legacy environment where compatibility with older APIs is confirmed. Avoid it if the organization has strict license compliance requirements (NOASSERTION is legally ambiguous), requires modern security/maintenance guarantees, or if Code Climate now offers an official/maintained alternative (e.g., their newer language-agnostic test reporter). For new projects or teams prioritizing long-term support, investigate actively maintained tools to avoid technical debt from outdated dependencies.
To executives: "This tool automates PHP test coverage reporting to Code Climate, providing real-time visibility into code quality trends and enabling data-driven quality gates without disrupting CI workflows. It reduces manual overhead, accelerates engineering accountability, and aligns with our broader quality observability strategy—turning test metrics into actionable business insights."
To engineering: "It’s a lightweight, zero-config CLI that seamlessly uploads PHPUnit Clover reports to Code Climate from your CI pipeline. However, given its 2017 release date and unlicensed status, we’ll need to validate compatibility with current Code Climate APIs and assess legal risks before adoption. If it works, it’s a quick win; if not, we’ll pivot to Code Climate’s official tools or modern alternatives."
How can I help you explore Laravel packages today?