<?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 Aftermarket.dev</title>
    <link>https://aftermarket.dev/tags/testing/</link>
    <description>Recent content in testing on Aftermarket.dev</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aftermarket.dev/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How AfterPatch Was Tested Before Its First Release</title>
      <link>https://aftermarket.dev/how-afterpatch-was-tested-before-its-first-release/</link>
      <pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/how-afterpatch-was-tested-before-its-first-release/</guid>
      <description>A repair tool earns trust in one way: it has to leave alone everything it isn&amp;rsquo;t supposed to touch. So most of the AfterPatch tests don&amp;rsquo;t check the repairs. They check what happens around them.
Every number here comes from the recorded results in the repository&amp;rsquo;s test/results folder, written by a script, not by hand.
The headline test The first test sends 400 random requests straight to a test server, then sends the same 400 through AfterPatch.</description>
    </item>
    
  </channel>
</rss>
