Who Owns Quality When AI Writes the Code?
Software QA moved into feature teams, test tooling, and production. See why AI gives the VP of Engineering a reason to fund verification across teams.
Browse 53 posts in this category
Software QA moved into feature teams, test tooling, and production. See why AI gives the VP of Engineering a reason to fund verification across teams.
Run the mock-lab LLM streaming lab: record streamed chat traffic with proxymock, replay it, and fail the run when TTFT or inter-token latency regresses.
Speedscale replays now measure AIPerf-defined TTFT, inter-token latency and token throughput on your recorded LLM traffic, next to what production measured.
AI writes code faster. Build autonomous verification with deterministic gates and LLM-powered tests to own reliability, scalability, and the consequences.
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.
Improve AI code reliability with reviewed requirements, preserved traffic baselines, and explicit replay gates. Reuse working examples before deploying.
Production AI spend gets attention. Non-prod LLM calls in development, CI, and load tests often do not. Simulation fixes that.
Test AI code in CI/CD with proxymock. Reuse recorded API traffic, prove a broken change fails, and keep replay reports for review before you deploy code.
Debug AI-generated code with proxymock: reproduce failing API calls, inspect response differences, preserve the baseline, and verify fixes before release.
Choose the desktop proxymock or the hosted cloud trial to get started.