Test and Mock GraphQL APIs Without Trusting the 200
Generate GraphQL tests and mocks from a schema with proxymock, catch failures hidden inside HTTP 200 responses, and flag schema changes before clients break.
Speedscale Blog
Latest insights on Agentic AI workflows, cloud native architectures, and performance optimization best practices from the Speedscale team.
Search answers across the full blog library
Featured Post
Recent Posts
Inside Kraken: Regression Testing With Traffic Replay
See how Kraken combines traffic replay, stable dependency mocks, and evolving regression coverage to catch Speedscale release failures before production.
Speedscale vs. Keploy: A Technical Comparison
Speedscale vs. Keploy: compare passive capture, protocol coverage, local replay, load testing, and data controls for production traffic testing.
gRPC Mocks, Tests and Contract Checks From a .proto
Turn a .proto file into gRPC mocks and tests with proxymock, record real responses, and catch field type changes that protobuf decoding silently accepts.
What Keploy Gets Wrong About Speedscale
Keploy's Speedscale comparison gets the architecture wrong. Check its claims against the docs for eBPF capture, TLS, automatic mocks, and local testing.
5 Questions to Ask Before the Next Cloud Outage
A power failure in one Google Cloud London zone took down banking apps for hours. Five questions to answer with real traffic before the next outage answers them for you.
Load Test One Endpoint, Watch the Rest
Load test one endpoint while keeping another steady. See how separate schedules and latency goals reveal slowdowns an overall average can hide.
Observability Never Really Shifted Left
We shifted testing, security, and CI/CD left. Observability stayed in production. With AI writing code faster, validation is the bottleneck.
Mock vs stub: differences and testing examples
A stub supplies responses; a mock verifies interactions. Compare both with runnable Python examples and learn when API traffic mocks help.
Postman load testing: a practical API tutorial
Run a Postman performance test, choose virtual users, inspect latency and errors, and isolate dependencies with recorded API mocks.