<?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 lqo.net</title>
    <link>https://lqo.net/tags/testing/</link>
    <description>Recent content in Testing on lqo.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://lqo.net/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How LQO Was Tested, From Writes It Must Never Run to Traps It Must Find</title>
      <link>https://lqo.net/how-lqo-was-tested-from-writes-it-must-never-run-to-traps-it-must-find/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://lqo.net/how-lqo-was-tested-from-writes-it-must-never-run-to-traps-it-must-find/</guid>
      <description>&lt;p&gt;A tool that runs your queries on a database has two jobs, and the first one matters more. It must never do harm: no writes, no settings left behind, no runaway query. Then it must actually find something. LQO&amp;rsquo;s tests go after both, against a real PostgreSQL server rather than a mock.&lt;/p&gt;&#xA;&lt;p&gt;All 62 tests pass in the recorded run, on a two-core cloud machine with PostgreSQL 16. CI runs them again on every change against PostgreSQL 14 and 18, and runs the parts that need no server on macOS and Windows. The logs are &lt;a href=&#34;https://github.com/learned-query-optimizer/lqo/tree/main/test/results&#34;&gt;on GitHub&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
