https://aftermarket.dev/tags/afterdiff/ Recent content in afterdiff on Aftermarket.dev Hugo -- gohugo.io en-us Tue, 20 Oct 2026 00:00:00 +0000 https://aftermarket.dev/aftertest-and-afterdiff-released-to-record-traffic-and-compare-versions/ Tue, 20 Oct 2026 00:00:00 +0000 https://aftermarket.dev/aftertest-and-afterdiff-released-to-record-traffic-and-compare-versions/ 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. https://aftermarket.dev/case-study-catching-a-renamed-field-before-release-with-aftertest-and-afterdiff/ Tue, 20 Oct 2026 00:00:00 +0000 https://aftermarket.dev/case-study-catching-a-renamed-field-before-release-with-aftertest-and-afterdiff/ 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’t control call it every day. Before switching, they want to know: does v2 answer the same questions the same way? https://aftermarket.dev/how-aftertest-and-afterdiff-were-tested-with-secrets-in-every-request/ Tue, 20 Oct 2026 00:00:00 +0000 https://aftermarket.dev/how-aftertest-and-afterdiff-were-tested-with-secrets-in-every-request/ 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.