Integration Test Authoring with Claude Code: Artifact Delivery
A production playbook for integration test authoring in cross-industry operations using Claude Code: artifact delivery, 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
Require Claude Code to write customer-visible files under /skill/output/artifacts, validate filenames and sizes, then return signed artifact metadata in argo.result.v1.
Tradeoffs and failure modes
Artifact policy constrains file output, but customers receive files that are durable, typed, and safe to download. 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.
Artifact manifest
artifacts:
- integration-test-authoring-summary.md
- integration-test-authoring-evidence.csv
- integration-test-authoring-review.json
signed_urls: true
retention: org_policy
Run this on Argo