<?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 KvSQL.com</title>
    <link>https://kvsql.com/tags/testing/</link>
    <description>Recent content in Testing on KvSQL.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 22 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://kvsql.com/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How KvSQL Was Tested With Power Cuts, Killed Processes and 30000 Statements Checked Against SQLite</title>
      <link>https://kvsql.com/how-kvsql-was-tested-with-power-cuts-killed-processes-and-30000-statements-checked-against-sqlite/</link>
      <pubDate>Thu, 22 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://kvsql.com/how-kvsql-was-tested-with-power-cuts-killed-processes-and-30000-statements-checked-against-sqlite/</guid>
      <description>&lt;p&gt;A database makes one promise above the rest. When it says a commit is done, the data is there, even if the power goes a moment later. And if the power goes during a commit, the file holds the whole transaction or none of it, never part. Most of KvSQL&amp;rsquo;s tests are aimed at that promise, from several sides.&lt;/p&gt;&#xA;&lt;p&gt;All the figures below come from one recorded run of the project&amp;rsquo;s test script, &lt;code&gt;scripts/record-results.sh&lt;/code&gt;, on a Linux container with two virtual CPUs, on October 22, 2026. The full output is in the repository under &lt;a href=&#34;https://github.com/softdevstudio/kvsql/tree/main/test/results/latest&#34;&gt;test/results/latest&lt;/a&gt;. CI runs the same script on Linux and macOS on every change.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
