Chronos Data Flow Test

Tests the full data flow through the Chronos Docker stack across multiple container states.

When invoked:

1. Run the data flow test script:

   bashCopy

   bash tooling/data-flow-test/test-data-flow.sh
   

2. Analyze the output and report:

   • Which containers are up/down
   • Whether the stack is running in standalone (no PostgreSQL) or full mode
   • Which tests passed, failed, or were skipped
   • Root cause analysis for any failures

3. If specific sections were requested, use the appropriate flag:

   • --state — container state only
   • --core — Core tests only
   • --query — Query Service tests only
   • --mcp — MCP tests only
   • --flow — end-to-end data flow only
   • --json — append for machine-readable output

Test Coverage

The script tests these data flow paths:

Common Failure Patterns

• Core DOWN, Query Service UP: Query Service health will show backend: degraded. Event proxy calls will fail.
• Query Service DOWN, Core UP: Direct Core tests pass. Flow test falls back to writing directly to Core.
• Standalone mode (no PostgreSQL): Tenant/usage endpoints return dev tenant. Usage metering is skipped. This is expected.
• 404 on Query Service endpoints: Route mismatch — check if MCP is using /api/v1/ paths instead of /api/ paths.

Environment Variables

Override default ports if your Docker mapping differs:

CORE_PORT=3280 QUERY_PORT=3283 MCP_PORT=3904 bash tooling/data-flow-test/test-data-flow.sh

Docker Compose

To bring the stack up/down for testing:

# Start
docker compose -f ~/Projects/alphaSigmaPro/wallet/docker/docker-compose.chronos.yml up -d

# Stop
docker compose -f ~/Projects/alphaSigmaPro/wallet/docker/docker-compose.chronos.yml down