<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Test Coverage on quanttype</title>
    <link>https://quanttype.net/tags/test-coverage/</link>
    <description>Recent content in Test Coverage on quanttype</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 09 May 2026 06:19:52 +0300</lastBuildDate>
    <atom:link href="https://quanttype.net/tags/test-coverage/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The joys of coverage</title>
      <link>https://quanttype.net/p/the-joys-of-coverage/</link>
      <pubDate>Thu, 10 Oct 2019 19:53:18 +0300</pubDate>
      <guid>https://quanttype.net/p/the-joys-of-coverage/</guid>
      <description>Tracking the code coverage is great (except that Clojure has some problems)</description>
    </item>
    <item>
      <title>The Law of Partial Test Coverage</title>
      <link>https://quanttype.net/p/law-of-partial-testing-coverage/</link>
      <pubDate>Mon, 08 Jun 2015 00:00:00 +0000</pubDate>
      <guid>https://quanttype.net/p/law-of-partial-testing-coverage/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve been thinking about unit tests lately. Here&amp;rsquo;s an observation I&#xA;made - I call it &lt;em&gt;the law of partial test coverage&lt;/em&gt;:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;When your test coverage is less than 100%, the most annoying bugs&#xA;will be in the untested part.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;Why is this? An obvious reason is that untested code is more likely to&#xA;have regressions. A more subtle reason is that it&amp;rsquo;s not random what&#xA;parts of the code are tested and what parts are not.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
