Automating API Mocks in Your CI Pipeline with proxymock
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.
Browse 76 posts in this category
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.
Export recorded HTTP requests to Postman collections. Add assertions, test credentials, and variables, then review updates before running in CI.
Combine load testing and mocks to isolate service performance. Learn when dependencies should stay real and how to avoid misleading capacity results.
Test gRPC streams with clear boundaries for recorded mocks, real message buses, cancellation, flow control, and supported streaming versions.
Calculate TPS from completed transactions and a measured time window. Distinguish requests, business outcomes, retries, latency, and errors.
Create ephemeral environments when deployed testing adds value. Version test data, define ownership and expiry, and verify cleanup of external resources.
Compare Kubernetes traffic capture tools, TLS visibility, setup permissions, and replay options. Choose packet inspection or decoded application traffic.
Validate Oracle JDK to OpenJDK migrations with traffic replay. Compare API behavior, check TLS connections, and measure repeatable performance results.
Use preview environments for branch review with explicit data, access, and dependency boundaries. Automate expiry and verify resource cleanup.
Choose the desktop proxymock or the hosted cloud trial to get started.