1,238 API errors in two days, and every response said 200 OK
We searched our own API traffic for gRPC errors hiding behind HTTP 200 and found five dashboard bugs that showed an empty screen instead of an error.
Co-founder and CEO of Speedscale, passionate about performance engineering. • 9 posts published
We searched our own API traffic for gRPC errors hiding behind HTTP 200 and found five dashboard bugs that showed an empty screen instead of an error.
Run recorded API mocks in GitHub Actions with proxymock. Use the existing Go demo, check response bodies, and connect the job to a reviewed replay baseline.
Production AI spend gets attention. Non-prod LLM calls in development, CI, and load tests often do not. Simulation fixes that.
Most flaky test fixes focus on retries and quarantine. The real fix is replacing hand-written test data with recorded traffic that stays fresh.
Compare WireMock alternatives by task: recorded mocks and replay with proxymock, HTTP expectations with MockServer, or contract-driven mocks with Microcks.
Create ephemeral environments when deployed testing adds value. Version test data, define ownership and expiry, and verify cleanup of external resources.
Record real LLM traffic from a FastAPI app, mock it locally, and replay it in CI with proxymock.
Replay an authenticated flow and the protected calls fail with 403. Here is how proxymock recommendations fix the expired bearer token in one click.
Learn how to test your React frontend without running backend services. Record real API traffic and mock responses for faster development, reliable.
Choose the desktop proxymock or the hosted cloud trial to get started.