Your First Useful Mock
Part 2 of Getting Started with Mocks: a test you cannot write, one seam, and the smallest mock that makes a delayed package happen. Java, Node, Go, Python.
Browse 104 posts in this category
Part 2 of Getting Started with Mocks: a test you cannot write, one seam, and the smallest mock that makes a delayed package happen. Java, Node, Go, Python.
Part 8 of Getting Started with Mocks: the carrier renames a field, production breaks, and every mocked test still passes. Java, Node, Go, Python.
A scoped chaos rule takes one dependency down and nothing else, so the fallback branch in your code executes on demand instead of during an outage.
Scoped chaos rules are now in proxymock: pick traffic with a filter query, perturb it, and label every injected failure so it is never mistaken for a real one.
I pointed a classifier at 7,943 API calls to find business workflows. It worked, then showed where my assumptions about sessions and patterns fell apart.
Infrastructure and application chaos break different layers and find different bugs. Netflix built two systems for a reason. Most enterprises buy just one.
Synthetic monitoring depends on scripts engineers maintain by hand. Capturing and replaying real production transactions turns customer behavior into tests.
A production bug survived two confident fixes and green tests. Replaying the captured request exposed the missing state and proved the real fix.
Testing AI applications with invented traffic looks fine until real users arrive. Then come the retries, the fallback models, and the token bill.