<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Test Quality on Nalar</title>
    <link>https://nalar.dev/tags/test-quality/</link>
    <description>Recent content in Test Quality on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/test-quality/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Use Mutation Testing to Find Weak Tests</title>
      <link>https://nalar.dev/use-mutation-testing-to-find-weak-tests/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/use-mutation-testing-to-find-weak-tests/</guid>
      <description>&lt;p&gt;A test suite can execute every line of an important function and still fail to detect that the function is wrong. Coverage tells you which code ran. It does not tell you whether the assertions would notice a meaningful defect in that code.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Mutation testing&lt;/strong&gt; approaches the problem from the other direction. A mutation testing tool makes small, deliberate changes to production code and runs the tests. If the tests fail, they detected the change. If the tests still pass, the altered behavior has exposed a possible weakness in the suite.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
