Two confident fixes missed this production bug
A production bug survived two confident fixes and green tests. Replaying the captured request exposed the missing state and proved the real fix.
Posts about api testing
Browse 88 posts in this category
Imaginary Test Data. Real Token Bill.
Testing AI applications with invented traffic looks fine until real users arrive. Then come the retries, the fallback models, and the token bill.
Top 14 Postman Alternatives for API Testing in 2026
A rebuilt 2026 guide to Postman alternatives. Which API clients are still maintained, what they cost, and which one fits local-first, gRPC, or team workflows.
Which Bugs AI Agents Fix Better With Traffic
A second run of our AI bug-fixing benchmark shows where captured traffic lifts agents toward 90%, why service maps barely help, and which bugs still fail.
Beware of PII in Testing Data: The Security Iceberg and Where PII Actually Hides
Using 'production-similar' data in pre-production is a major security risk. Learn why traditional masking fails, where hidden PII hides, and how to fix it.
Build WireMock mappings fast from real traffic
Skip hand-writing WireMock stubs. Speedscale records your real request and response traffic and exports it straight to WireMock mappings.
Five things your logs will never tell you
Logs, metrics, and traces are a lossy compression of production. Five things you can do with a traffic data lake that observability can't.
Fixing 403 auth errors when you replay traffic
Replay an authenticated flow and the protected calls fail with 403. Here is how proxymock recommendations fix the expired bearer token in one click.
Capture once, test forever
Production traffic is the most complete record of what your system does, and most teams throw it away. One capture powers reproduce, validate, and sandbox.