<?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 HyperCrux.com</title>
    <link>https://hypercrux.com/tags/testing/</link>
    <description>Recent content in Testing on HyperCrux.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 06 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://hypercrux.com/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How HyperCrux Was Tested: 200 Killed Writers and Not One Mismatched Record</title>
      <link>https://hypercrux.com/how-hypercrux-was-tested-200-killed-writers-and-not-one-mismatched-record/</link>
      <pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://hypercrux.com/how-hypercrux-was-tested-200-killed-writers-and-not-one-mismatched-record/</guid>
      <description>&lt;p&gt;HyperCrux makes one promise above the others. A record can be reached four ways, by key, by SQL, by its links and by its vector, and the four never disagree. A deleted record doesn&amp;rsquo;t linger in search results. A link never points at a record that isn&amp;rsquo;t there. A vector never belongs to a row that was only half written.&lt;/p&gt;&#xA;&lt;p&gt;Promises like that are easy to make when nothing goes wrong. So the tests go looking for things going wrong, and the results are published with the code, in &lt;a href=&#34;https://github.com/hypercrux/hypercrux/tree/main/test/results&#34;&gt;test/results on GitHub&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
