Tag
afterdiff
Aftermarket 0.10.0 adds aftermarket shadow. It’s AfterDiff, but on live traffic instead of a recording. Replay is good at one thing. You record what a client sends, …
afterdiff
Aftermarket 0.10.1 is a fix release for aftermarket shadow, the live mode of AfterDiff that came out earlier today. A second reviewer went through it looking for ways to …
afterbridge
AfterBridge makes four promises. The files it reads are never written. Nothing a request sends reaches SQL or the file system. A file that is half written is never …
afterconfig
AfterConfig makes four promises, and the tests go after each one. It never writes the vendor’s file. It never changes what the overlay doesn’t name. A failed …
afterguard
A security gateway is only as good as its worst gap, so AfterGuard got a written threat model before any code, and every promise in it got a test. Six promises: nothing …
afterhook
AfterHook makes four promises. Every change gives exactly one event. Nothing is lost while the receiver is down or across restarts. A source that didn’t change by …
afterschema
AfterSchema makes two promises that matter. It never writes a database. And when schema test says an old read gives the same rows through the views, it does: same values, …
afterconfig
TOML in AfterConfig makes one promise on top of the old ones: the output is the vendor’s file with only your changes in it. Comments, spacing and every untouched …
afterapi
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
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
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. …