Stop dynamic IDs from breaking your integration tests! Tired of manual copy-pasting for IDs in your test cycles? Learn how to use proxymock to help: Check out proxymock.io to get started for free!
Learn how to resolve the 403 authentication error when replaying API traffic using proxymock. This video demonstrates how to: All tools and demo code are open source and available on GitHub. For more information, visit proxymock.io.
This video demonstrates how to use Proxymock, a free tool designed to record API calls. Learn more by watching the full video or visiting proxymock.io.
Stop letting broken downstream dependencies kill your workflow. Use proxymock to record backend data and inbound calls, then flip on a mock whenever a system goes offline. You can even replay traffic to test your code changes and ensure your endpoints are still working perfectly.
AI can write a feature in seconds, but where are you testing it? Sending production traffic, API payloads, and auth headers to a third-party SaaS is a massive security risk. In this video, we break down why the Bring Your Own Cloud (BYOC) model is the ultimate fix for DevSecOps. Learn how to safely test AI-generated code against real production traffic entirely within your own VPC or Kubernetes cluster. No data leaks, no massive DLP pipelines, and no endless masking rules.
Your logs showed 500 errors. The traces showed the dependency graph. Neither showed the actual bug, a DEL control character getting appended to the query string. This is how I found it. In this video I walk through Speedscale BYOC (bring your own cloud): capture real production traffic, store it in your own Elasticsearch cluster inside your VPC, pull it down locally with a single script, and reproduce the exact bug using proxymock. The data never leaves your environment.