<?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 Was Tested</title>
      <link>https://bitspeed.org/how-bitspeed-inspect-was-tested/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bitspeed.org/how-bitspeed-inspect-was-tested/</guid>
      <description>&lt;p&gt;Inspect&amp;rsquo;s tests challenge its explanations as well as its ability to complete a request. Controlled local endpoints delay headers, stream bodies, redirect, return empty responses, disconnect early and wait for cancellation. A report that explains only a successful request would miss a large part of the job.&lt;/p&gt;&#xA;&lt;p&gt;The test suite checks timing arithmetic, missing events, partial observations, source evidence links and privacy boundaries. Comparison tests cover changed payloads and encodings, mixed failures, zero baselines, insufficient coverage and overlapping ranges. The conditions and outcomes are kept in &lt;a href=&#34;https://github.com/softdevstudio/bitspeed/tree/main/test/results&#34;&gt;recorded results&lt;/a&gt;, rather than being turned into a generic speed claim.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
