<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>aftertest on Aftermarket.dev</title>
    <link>https://aftermarket.dev/tags/aftertest/</link>
    <description>Recent content in aftertest on Aftermarket.dev</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aftermarket.dev/tags/aftertest/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AfterDiff Gets a Live Shadow Mode to Test New Versions on Real Traffic</title>
      <link>https://aftermarket.dev/afterdiff-gets-a-live-shadow-mode-to-test-new-versions-on-real-traffic/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/afterdiff-gets-a-live-shadow-mode-to-test-new-versions-on-real-traffic/</guid>
      <description>Aftermarket 0.10.0 adds aftermarket shadow. It&amp;rsquo;s AfterDiff, but on live traffic instead of a recording.
Replay is good at one thing. You record what a client sends, play it to the old and the new version, and read the differences. But a recording only holds what happened while it ran. The odd request that comes once a week isn&amp;rsquo;t in the file, and neither is the client nobody remembered.
Shadow puts the new version next to the old one while real users keep going.</description>
    </item>
    
    <item>
      <title>Shadow Mode Recipes for Testing a New Version on Live Traffic</title>
      <link>https://aftermarket.dev/shadow-mode-recipes-for-testing-a-new-version-on-live-traffic/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/shadow-mode-recipes-for-testing-a-new-version-on-live-traffic/</guid>
      <description>Short, practical setups for aftermarket shadow, each one run before it went here. The commands come from runs of the downloaded 0.10.1 against Datasette, JSON Server and the customer-api example, recorded under test/results/case-studies/shadow in the code repository. In all of them the primary is the version clients use today and the candidate is the new one.
Shadow a rewrite Start with reads only. That&amp;rsquo;s the default, and it can&amp;rsquo;t change anything on the candidate:</description>
    </item>
    
    <item>
      <title>Aftermarket Fixes Proxy Answers Cut Off Under Load</title>
      <link>https://aftermarket.dev/aftermarket-fixes-proxy-answers-cut-off-under-load/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/aftermarket-fixes-proxy-answers-cut-off-under-load/</guid>
      <description>Aftermarket 0.7.1 is a fix release, and the bug it fixes was hiding in plain sight. For a couple of days CI failed now and then in the random pass-through tests, with an &amp;ldquo;unexpected EOF&amp;rdquo; while reading an answer. The same tests passed every time on the build machine. It got written off as a flaky test.
It wasn&amp;rsquo;t. Every failure was on the call through the proxy, never on the direct one.</description>
    </item>
    
    <item>
      <title>Aftermarket Hardens Patch, Adapt and Record Against Stalled and Cut Off Uploads</title>
      <link>https://aftermarket.dev/aftermarket-hardens-patch-adapt-and-record-against-stalled-and-cut-off-uploads/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/aftermarket-hardens-patch-adapt-and-record-against-stalled-and-cut-off-uploads/</guid>
      <description>Aftermarket 0.7.2 is about one unglamorous thing: what a proxy does with a request body that doesn&amp;rsquo;t arrive the normal way. It might come slowly, stop halfway, get cut off, or still be on its way when the upstream has already answered.
That sounds like an edge case. It isn&amp;rsquo;t, once a proxy sits in front of real clients. Phones lose signal mid-upload. Scripts get killed. Some servers answer 401 before reading a byte of the body.</description>
    </item>
    
    <item>
      <title>AfterTest and AfterDiff Released to Record Traffic and Compare Versions</title>
      <link>https://aftermarket.dev/aftertest-and-afterdiff-released-to-record-traffic-and-compare-versions/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/aftertest-and-afterdiff-released-to-record-traffic-and-compare-versions/</guid>
      <description>Aftermarket 0.3.0 adds two tools that work as a pair. AfterTest, run as aftermarket record, saves real traffic as test fixtures. AfterDiff, run as aftermarket replay, sends those fixtures to two versions of a service and tells you where the answers differ.
The first two tools fix things. These two answer the question that comes before any fix: what actually changed? A new release, a migrated service or a rewritten endpoint can look the same in the docs and still answer differently.</description>
    </item>
    
    <item>
      <title>Case Study: Catching a Renamed Field Before Release With AfterTest and AfterDiff</title>
      <link>https://aftermarket.dev/case-study-catching-a-renamed-field-before-release-with-aftertest-and-afterdiff/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/case-study-catching-a-renamed-field-before-release-with-aftertest-and-afterdiff/</guid>
      <description>This is a worked case on two small stand-in versions of an orders service. Every command and every line of output below comes from a real run of aftermarket 0.3.0.
The question A team is about to replace version 1 of an orders service with version 2. The release notes say nothing about the API. Clients they don&amp;rsquo;t control call it every day. Before switching, they want to know: does v2 answer the same questions the same way?</description>
    </item>
    
    <item>
      <title>How AfterTest and AfterDiff Were Tested With Secrets in Every Request</title>
      <link>https://aftermarket.dev/how-aftertest-and-afterdiff-were-tested-with-secrets-in-every-request/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aftermarket.dev/how-aftertest-and-afterdiff-were-tested-with-secrets-in-every-request/</guid>
      <description>A recorder sits on real traffic and writes it to disk. So it makes two promises, and the tests go after both. It must not change a single byte on the way through. And no secret may end up in the file.
Not a byte changed One test sends 300 random requests straight to a test server and then through record, and compares what each side saw. The traffic is deliberately awkward: binary bodies, gzip, chunked bodies, bodies of unknown length, %2F and ü in paths, ; in query strings, HEAD, 204 and 304.</description>
    </item>
    
  </channel>
</rss>
