<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Unit Testing on Nalar</title>
    <link>https://nalar.dev/tags/unit-testing/</link>
    <description>Recent content in Unit Testing on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 10 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/unit-testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Choosing Sociable or Solitary Unit Tests</title>
      <link>https://nalar.dev/choosing-sociable-or-solitary-unit-tests/</link>
      <pubDate>Thu, 10 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/choosing-sociable-or-solitary-unit-tests/</guid>
      <description>&lt;h1 id=&#34;choosing-sociable-or-solitary-unit-tests&#34;&gt;Choosing Sociable or Solitary Unit Tests&lt;/h1&gt;&#xA;&lt;p&gt;A unit test fails after a harmless refactor. The production behaviour is still correct, but the test expected an internal collaborator to receive exactly three calls. Elsewhere, a different unit test passes even though two real classes no longer work together, because both sides were replaced with mocks.&lt;/p&gt;&#xA;&lt;p&gt;Both tests are isolated in some sense, yet they give poor feedback for different reasons. The useful question isn&amp;rsquo;t simply whether unit tests should use mocks. It is &lt;strong&gt;where the test boundary should be&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
