Integration Test Authoring with Claude Code: Cost Controls
A production playbook for integration test authoring in cross-industry operations using Claude Code: cost controls, run-scoped inputs, logs, typed results, and artifacts.
Audience: Engineering teams improving coverage
The problem
Engineering teams improving coverage need integration test authoring to run repeatedly against API routes, fixtures, logs, and failure modes. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Set explicit limits for integration test authoring: input size, run time, tool calls, artifacts, retries, and concurrent runs per organization.
Tradeoffs and failure modes
Limits reject pathological runs, but they keep one workflow from turning into an unbounded infrastructure bill. For integration test authoring, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Run limits
max_run_seconds=1800
max_input_bytes=104857600
max_artifact_bytes=104857600
max_tool_calls=120
retry_after_seconds=60
Run this on Argo