Skip to main content

Engine Test Area

Root-level tests should exercise deployed application behavior through public HTTP contracts, Compose, Helm, or Kubernetes.

Service unit tests belong inside the owning application, for example:

  • engine/internal/...
  • services/auth/internal/...
  • services/runtime/internal/...
  • services/ai/internal/...
  • services/mcp/internal/...
  • services/usage/internal/...

Do not import another application's internal package from here. That would break the microservice boundary.

Production verification entry points​

Run ./scripts/verify-production-gates.sh from the ACP Engine source root for Go, SDK, ADK, Manager, API parity, and Compose checks. Set ACP_RUN_LIVE_E2E=1 only with scoped credentials from an untracked environment to add public-contract runtime, trace, usage, cross-realm, and merchant/store checks.

Reusable fake AI and MCP servers live under backend/verification/fakes and support deterministic outage, latency, cancellation, pagination, session, schema, and idempotency scenarios. ./scripts/run-load-soak.sh runs the repeatable local MCP benchmark; target-environment queue, worker, database, and network chaos must be executed in an approved window.

See Production Readiness and Validation for release evidence and project-specific acceptance requirements.