api-integration-test

API Integration Test

Goal

Build production-representative, opt-in integration tests for internal APIs with strict safety controls, reproducible execution, and clear failure diagnosis.

When To Use

Trigger this skill when the user asks for:

• Internal API integration tests (HTTP or gRPC)
• Service-to-service adapter tests requiring real runtime config
• Internal endpoint contract verification against real responses
• Integration test failure triage or debugging

Scope

Use this skill for:

1. Internal HTTP API integration tests.
2. Internal gRPC client/server integration tests.
3. Service-to-service adapter tests requiring real runtime config.
4. Internal endpoint contract verification against real responses.

Do not use this skill for:

1. Pure unit tests with heavy mocks — use $unit-test.
2. Full end-to-end browser journeys.
3. Third-party vendor API tests — use $thirdparty-api-integration-test.

Mandatory Gates

Gates execute in strict serial order. Any gate failure blocks all subsequent steps.

1) Scope        2) Go Version   3) Config       4) Mode
   Validation ──→  Gate       ──→  Completeness ──→  Selection
   │               │               │                │
   out of scope?   read go.mod    Full/Scaffold/   auto-select
   → stop+redirect → adapt        Blocked?         Smoke/Std/Comp
                                   Blocked → STOP
        │               │               │                │
        5) Production   6) Execution    7) Reference
           Safety     ──→  Integrity  ──→  Loading
           │               │               │
           prod? env+host  actually ran?   load by trigger
           → t.Fatalf      → report        pattern

1) Scope Validation Gate

Confirm the task falls within this skill's scope:

• Internal HTTP or gRPC API → proceed
• Pure unit test → redirect to $unit-test, STOP
• Third-party vendor API → redirect to $thirdparty-api-integration-test, STOP
• Full end-to-end browser journey → out of scope, inform user, STOP