<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Branch-Coverage on Codeslog</title>
    <link>https://www.codeslog.com/en/tags/branch-coverage/</link>
    <description>Recent content in Branch-Coverage on Codeslog</description>
    <image>
      <title>Codeslog</title>
      <url>https://www.codeslog.com/images/default-cover.png?v=20260114T1436</url>
      <link>https://www.codeslog.com/images/default-cover.png?v=20260114T1436</link>
    </image>
    <generator>Hugo -- 0.150.0</generator>
    <language>en-US</language>
    <lastBuildDate>Tue, 04 Aug 2026 09:08:00 +0900</lastBuildDate>
    <atom:link href="https://www.codeslog.com/en/tags/branch-coverage/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Read Coverage — and the Metrics Beyond It</title>
      <link>https://www.codeslog.com/en/posts/frontend-testing-coverage-metrics/</link>
      <pubDate>Tue, 04 Aug 2026 09:08:00 +0900</pubDate>
      <guid>https://www.codeslog.com/en/posts/frontend-testing-coverage-metrics/</guid>
      <description>How should you read a coverage report, and how far should you trust it? The difference between line and branch coverage, finding untested forks, and the team-health metrics numbers can&amp;#39;t show.</description>
    </item>
  </channel>
</rss>
