<?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 CodeInstances.com</title>
    <link>https://codeinstances.com/tags/testing/</link>
    <description>Recent content in Testing 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/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How CodeInstances Was Tested Before Its First Release</title>
      <link>https://codeinstances.com/how-codeinstances-was-tested-before-its-first-release/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://codeinstances.com/how-codeinstances-was-tested-before-its-first-release/</guid>
      <description>&lt;p&gt;A tool that claims to replay runs exactly has to be tested on exactly that. So most of the testing for v0.1.0 does the same thing over and over in different ways: record a program against real servers, shut the servers down, replay it, and check the replay came out the same. Then change something and check the replay notices.&lt;/p&gt;&#xA;&lt;p&gt;Every number in this post comes from the result files in the code repository, in &lt;a href=&#34;https://github.com/codeinstances/codeinstances/tree/main/test/results&#34;&gt;test/results&lt;/a&gt;. They were recorded on October 18, 2026, at commit c2a5975, on a Linux machine with an Intel Xeon processor at 2.10GHz and 2 CPUs, with Go 1.24.7. One script, &lt;code&gt;scripts/record-tests.sh&lt;/code&gt;, runs everything and writes the files, so anyone can run it again.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
