case studies
Case Study: Moving an Old Client to a New Customer API With AfterAPI
This case uses the examples/customer-api folder from the code repository, so you can run every step yourself. The commands and output below come from a real run of …
Posts
afterapi
How AfterAPI Was Tested Against an Old Client Test Suite
AfterAPI makes one main promise: an old client keeps working against a new API, and nothing it doesn’t cover gets touched. The tests were written to try to break …
aftertest
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 …
afterpatch
AfterPatch Released as the First Aftermarket Tool
AfterPatch 0.1.0 is out. It’s the first working tool in the Aftermarket family: a small reverse proxy that repairs HTTP traffic between a client and a service, with …
afterpatch
How AfterPatch Was Tested Before Its First Release
A repair tool earns trust in one way: it has to leave alone everything it isn’t supposed to touch. So most of the AfterPatch tests don’t check the repairs. …
explainer
What a Software Aftermarket Is and Why You Already Use One
Every developer has fixed software they didn’t write. Most of us just don’t call it that. You put nginx in front of an old app to add a header it forgot. You …
about
Why Aftermarket Is Named After Car Parts
The name came first, before any code. It describes a category that already exists in software but doesn’t have a word of its own. Car people know the word well. The …
afterpatch
Why Aftermarket starts with one patch
A software aftermarket sounds like a place where you can bolt on anything. That makes a good name and a terrible first specification. A pile of adapters, shims and rescue …