<?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 BitSpeed.org</title>
    <link>https://bitspeed.org/tags/testing/</link>
    <description>Recent content in Testing on BitSpeed.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 20 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bitspeed.org/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How BitSpeed Inspect and Transfer Were Tested</title>
      <link>https://bitspeed.org/how-bitspeed-inspect-and-transfer-were-tested/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bitspeed.org/how-bitspeed-inspect-and-transfer-were-tested/</guid>
      <description>&lt;p&gt;Each tool makes one main promise, and the tests go after that promise first. Inspect promises to explain where observed request time went without inventing a cause. Transfer promises that an interrupted file transfer resumes from verified pieces and ends in one complete, checked file. Happy paths are covered too. They just aren&amp;rsquo;t where the effort went.&lt;/p&gt;&#xA;&lt;p&gt;Every push to main runs the full suite on Linux and macOS: formatting, go vet, race-enabled tests, both command builds and smoke checks against the built executables. The outcomes are written to &lt;a href=&#34;https://github.com/softdevstudio/bitspeed/tree/main/test/results&#34;&gt;recorded results&lt;/a&gt; with the Go version, platform and a fingerprint of the source tree.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
