<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Testing on Bootstrapping.org</title>
    <link>https://bootstrapping.org/tags/testing/</link>
    <description>Recent content in Testing on Bootstrapping.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bootstrapping.org/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Bootstrapping Was Tested With 400 Killed Applies and Half a Million Checked Values</title>
      <link>https://bootstrapping.org/how-bootstrapping-was-tested-with-400-killed-applies-and-half-a-million-checked-values/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bootstrapping.org/how-bootstrapping-was-tested-with-400-killed-applies-and-half-a-million-checked-values/</guid>
      <description>&lt;p&gt;A tool that writes to customers&amp;rsquo; databases on every release makes a few promises, and each one is the kind you only find broken in production. An admin&amp;rsquo;s edit is never overwritten without a conflict being raised. A change in the seed to a value nobody touched always lands. An apply happens completely or not at all, even if the process dies. Two deploys at once don&amp;rsquo;t both write. And a value means the same thing to Bootstrapping as it does to SQLite. Each of those got a test built to break it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
