<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code-Coverage on PlumePHP</title><link>https://plumephp.com/tags/code-coverage/</link><description>Recent content in Code-Coverage on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Tue, 22 Sep 2026 10:00:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/code-coverage/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub Actions 测试报告与覆盖率集成：从 JUnit 到 Codecov 的质量门禁</title><link>https://plumephp.com/github-actions-test-coverage-integration/</link><pubDate>Tue, 22 Sep 2026 10:00:00 +0800</pubDate><guid>https://plumephp.com/github-actions-test-coverage-integration/</guid><description>&lt;blockquote&gt;
&lt;p&gt;测试写得再多，如果无法直观地看到「哪些代码没被测到」「这次 PR 让覆盖率上升还是下降」，测试的投资回报率就会大打折扣。GitHub Actions 通过自动化流水线将测试执行与报告生成无缝衔接，配合覆盖率工具与 PR 评论集成，可以把「代码质量」从开发者的个人习惯升级为团队级别的硬性门禁。&lt;/p&gt;</description></item></channel></rss>