ke2e

Set the port variable from .devops-ai/infra.toml to your sandbox port (find it with kinfra status), then invoke the test runner with the test name. Pre-flight checks verify the container is running and the health endpoint returns HTTP 200 before any test steps execute.

Use the provided TEMPLATE.md structure: define pre-flight checks, test data, curl-based execution steps, success criteria, and sanity checks that catch false positives. The designer agent writes recipes to .claude/skills/ke2e/tests/{category}/{name}.md when no catalog match exists.

E2E tests make real API calls to a running container, observe real state changes via docker exec or API responses, and assert on real data. Integration tests with mocked externals are explicitly not E2E and should never be labeled as such.

Connection refused usually means the sandbox container is not running, fixable with kinfra sandbox start. Testing against the production default port instead of the sandbox port (base plus slot id) is a common configuration error caught by pre-flight checks.

Failures are classified as ENVIRONMENT, CONFIGURATION, CODE_BUG, or TEST_ISSUE using a decision tree. Each category has a report format with diagnosis and suggested action, plus symptom-to-cure mappings with retry limits for infrastructure issues.

Yes, but cold starts on LLM-backed services can take 200-400 seconds, so set timeouts accordingly (e.g., 600s) or use a session warmup preflight module. For non-deterministic LLM output, assert on structure like fields and status codes rather than exact content.