A Developer's Guide to Continuous Performance Testing
Add continuous performance tests to CI with bounded smoke checks and scheduled load runs. Choose meaningful gates and handle noisy results with baselines.
Browse 46 posts in this category
Add continuous performance tests to CI with bounded smoke checks and scheduled load runs. Choose meaningful gates and handle noisy results with baselines.
Choose API testing tools for exploration, CI regression, and dependency isolation. Compare assertions, protocols, workflows, and migration requirements.
Measure throughput with defined transaction boundaries, sustainable load stages, latency and error goals, and enough load-generator capacity.
Calculate TPS from completed transactions and a measured time window. Distinguish requests, business outcomes, retries, latency, and errors.
Compare GoReplay and Speedscale capture, TLS requirements, dependency mocks, and local or Kubernetes replay. Verify the exact workflow before choosing.
Test Kubernetes autoscaling with controlled load. Verify HPA metrics, readiness, scaling policies, and scale-down alongside latency and errors.
Run a Kubernetes load-test tutorial with recorded traffic. Check cluster prerequisites, dependency coverage, and data reset before repeating a replay.
Plan Kubernetes load tests with clear workload models, isolated dependencies, and measured generator capacity. Compare tools and read results in context.
Compare Speedscale and k6 for Kubernetes load testing. Reuse captured requests, isolate dependencies, and evaluate CI gates with the same workload.
Choose the desktop proxymock or the hosted cloud trial to get started.