<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Shrink on CodeInstances.com</title>
    <link>https://codeinstances.com/tags/shrink/</link>
    <description>Recent content in Shrink on CodeInstances.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://codeinstances.com/tags/shrink/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CodeInstances Shrinks a Failing Run to the Answer That Breaks It and Keeps It as a Test</title>
      <link>https://codeinstances.com/codeinstances-shrinks-a-failing-run-to-the-answer-that-breaks-it-and-keeps-it-as-a-test/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://codeinstances.com/codeinstances-shrinks-a-failing-run-to-the-answer-that-breaks-it-and-keeps-it-as-a-test/</guid>
      <description>&lt;p&gt;CodeInstances v0.3.0 adds two verbs at once. &lt;code&gt;codeinstances shrink&lt;/code&gt; takes a failing run and a passing one and finds which of the failing run&amp;rsquo;s answers actually cause the failure. &lt;code&gt;codeinstances test&lt;/code&gt; replays a folder of instances as regression tests. They belong together: the first finds the bug&amp;rsquo;s smallest form, the second makes sure it stays fixed.&lt;/p&gt;&#xA;&lt;p&gt;Here&amp;rsquo;s the problem shrink goes after. You&amp;rsquo;ve got a run that fails and one that doesn&amp;rsquo;t, and &lt;code&gt;diff&lt;/code&gt; from the last release shows you how they differ. Often that&amp;rsquo;s dozens of answers: timestamps, ids, counters, prices that moved. One of them broke the program, and the rest is noise. Reading them one by one is slow, and it&amp;rsquo;s guesswork.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
