<?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>코드커버리지 on Codeslog</title>
    <link>https://www.codeslog.com/tags/%EC%BD%94%EB%93%9C%EC%BB%A4%EB%B2%84%EB%A6%AC%EC%A7%80/</link>
    <description>Recent content in 코드커버리지 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>ko</language>
    <lastBuildDate>Sun, 05 Jul 2026 11:00:00 +0900</lastBuildDate>
    <atom:link href="https://www.codeslog.com/tags/%EC%BD%94%EB%93%9C%EC%BB%A4%EB%B2%84%EB%A6%AC%EC%A7%80/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>무엇을 얼마나 테스트할까 — 커버리지 100%의 함정</title>
      <link>https://www.codeslog.com/posts/frontend-testing-strategy-coverage/</link>
      <pubDate>Sat, 04 Jul 2026 22:34:00 +0900</pubDate>
      <guid>https://www.codeslog.com/posts/frontend-testing-strategy-coverage/</guid>
      <description>테스트는 많이 짤수록 좋은 걸까요? 무엇을 먼저 테스트할지 판단하는 기준과, 커버리지 숫자에 속지 않는 법을 정리합니다.</description>
    </item>
  </channel>
</rss>
