Layer 1: Platform Check    → Is the pod running? Replicas healthy?
Layer 2: Health Check      → Does the endpoint respond with 200?
Layer 3: Endpoint Tests    → Do the app's routes return expected responses?
Layer 4: Load Soak         → (Optional) Does it hold up under repeated requests?

tfy_applications_list(filters={"workspace_fqn": "WORKSPACE_FQN", "application_name": "APP_NAME"})

TFY_API_SH=~/.claude/skills/truefoundry-service-test/scripts/tfy-api.sh

# Get app status
$TFY_API_SH GET '/api/svc/v1/apps?workspaceFqn=WORKSPACE_FQN&applicationName=APP_NAME'

ports[0].host → https://{host}

{app-name}.{workspace-namespace}.svc.cluster.local:{port}

# HOST must be extracted from the app's ports[].host field (Layer 1).
# Never pass unvalidated user input directly as HOST.
# Try common health endpoints in order
curl -sf -o /dev/null -w '%{http_code} %{time_total}s' --max-time 10 "https://${HOST}/health"
curl -sf -o /dev/null -w '%{http_code} %{time_total}s' --max-time 10 "https://${HOST}/healthz"
curl -sf -o /dev/null -w '%{http_code} %{time_total}s' --max-time 10 "https://${HOST}/"

Health Check: https://my-app.example.cloud/health
  Status: 200 OK
  Response Time: 45ms
  Body: {"status": "ok"}

# Test root endpoint
curl -sf --max-time 10 "https://${HOST}/"

# Test OpenAPI docs (FastAPI)
curl -sf -o /dev/null -w '%{http_code}' --max-time 10 "https://${HOST}/docs"
curl -sf -o /dev/null -w '%{http_code}' --max-time 10 "https://${HOST}/openapi.json"

REST API Test: https://my-api.example.cloud
  Root (/): 200 OK — {"message": "hello"}
  Docs (/docs): 200 OK — Swagger UI available
  OpenAPI (/openapi.json): 200 OK — 12 endpoints documented

# Test root
curl -sf -o /dev/null -w '%{http_code} %{size_download}bytes %{time_total}s' --max-time 10 "https://${HOST}/"

Web App Test: https://my-app.example.cloud
  Root (/): 200 OK — 14832 bytes, 0.23s
  Content-Type: text/html

# For each endpoint the user specifies
curl -sf -w '\n%{http_code} %{time_total}s' --max-time 10 "https://${HOST}/${ENDPOINT}"

# Run 10 sequential requests to the health endpoint
for i in $(seq 1 10); do
  curl -sf -o /dev/null -w '%{time_total}\n' --max-time 10 "https://${HOST}/health"
done

Load Soak: 10 sequential requests to /health
  Min:  0.041s
  Avg:  0.048s
  Max:  0.062s
  P95:  0.059s
  Errors: 0/10

# Run 10 concurrent requests using background processes
for i in $(seq 1 10); do
  curl -sf -o /dev/null -w '%{http_code} %{time_total}\n' --max-time 10 "https://${HOST}/health" &
done
wait

Service Test Report: my-app
============================================================

Platform:
  Status: RUNNING
  Replicas: 2/2 ready
  Last Deployed: 2026-02-14 10:30 UTC

Health Check:
  Endpoint: https://my-app.example.cloud/health
  Status: 200 OK
  Response Time: 45ms

Endpoint Tests:
  GET /         → 200 OK (12ms)
  GET /docs     → 200 OK (85ms)
  GET /health   → 200 OK (45ms)

Load Soak (10 requests):
  Avg: 48ms | P95: 59ms | Max: 62ms | Errors: 0/10

Result: ALL PASSED

Result: FAILED at Layer 2 (Health Check)
  Error: 502 Bad Gateway
  Action: Check logs with the logs skill — likely a crash on startup

Could not find a public URL for this application.
The service may be internal-only (no host configured in ports).

Options:
- If this is intentional, the service can only be tested from within the cluster
- To expose it publicly, redeploy with a host configured (use `deploy` skill)

SSL certificate error when connecting to the endpoint.
This usually means the service was just deployed and the certificate hasn't provisioned yet.
Wait 2-3 minutes and retry.

All endpoints timed out (10s).
Possible causes:
- App is still starting up (check logs)
- App is listening on wrong port
- Network issue between you and the cluster
Action: Use logs skill to check if the app started successfully.

Endpoint requires authentication.
Provide auth details:
- For API key auth: set the key in an environment variable, then pass --header "Authorization: Bearer $YOUR_API_KEY"
- For TrueFoundry auth: the endpoint may need TFY_API_KEY as a header