xq-infra CLI

CLI for running local test environments: database, backend services, and gateway. Required for component and integration tests that hit real APIs.

Installation

npm install -g @chauhaidang/xq-test-infra@1.0.3

Requires GitHub Packages access (registry-url: https://npm.pkg.github.com/, scope @chauhaidang). Set NODE_AUTH_TOKEN or .npmrc if auth fails.

Core Commands

Important: Run xq-infra from the directory that contains test-env/. Do not use a different path.

Workflow: Write-Service Component Tests

From write-service/ (same directory as test-env/):

# 1. Build the service container image
./build-write-service.sh

# 2. Generate API client and install dependencies
npm run generate:client
npm install

# 3. Start test environment
xq-infra generate -f ./test-env
xq-infra up

# 4. Run component tests
npm run test:component:ci
# or: npm run test:component

# 5. Tear down (when done)
xq-infra down

Defaults: API_BASE_URL=http://localhost:8080/xq-fitness-write-service/api/v1, HEALTH_CHECK_URL=http://localhost:8080/xq-fitness-write-service/health.

Workflow: Other Services (e.g. Mobile)

From the directory that contains test-env/ (e.g. mobile/):

xq-infra generate -f ./test-env
xq-infra up
# Run tests...
xq-infra down

test-env Structure

Typical files:

Write-service test-env: xq.config.yml, xq-fitness-db.service.yml, xq-fitness-write-service.service.yml.

Gateway URLs

Tests use the gateway on port 8080:

• •Write: ${GATEWAY_URL}/xq-fitness-write-service/api/v1
• •Read: ${GATEWAY_URL}/xq-fitness-read-service/api/v1 (if present)

Port Conflicts

If startup fails or you see "address already in use":

1. •Check for other stacks (read-service, write-service, mobile) using the same ports
2. •Run xq-infra down in those project directories
3. •Avoid running multiple test envs that share ports (5432, 8080)

CI Usage

- run: npm install -g @chauhaidang/xq-test-infra@1.0.3
- run: xq-infra generate -f ./test-env && xq-infra up
- run: npm run test:component:ci
- if: always()
  run: |
    xq-infra logs
    xq-infra down

Troubleshooting