284313f908
Some checks are pending
Bidi Control Character Guard / bidi-control-guard (push) Waiting to run
Circular Dependency Check / Check for new circular dependencies (push) Waiting to run
Citus Migration Smoke / Combined migrations on single-node Citus (push) Waiting to run
E2E Fresh Install Tests / fresh-install-e2e (push) Waiting to run
ext-v2 guardrails / Run ext-v2 guard and ESLint (push) Waiting to run
Integration Tests / Check for relevant changes (push) Waiting to run
Integration Tests / ${{ (github.event_name == 'schedule' || github.event.inputs.suite == 'full') && 'Full integration suite' || 'Tier-1 integration subset' }} (push) Blocked by required conditions
Mobile checks / Mobile lint + typecheck (push) Waiting to run
Mobile checks / Mobile unit tests (push) Waiting to run
Mobile checks / Mobile dependency audit (report) (push) Waiting to run
Mobile checks / Mobile reproducibility checks (push) Waiting to run
Secrets guard (env backups) / Ensure no tracked env backup files (push) Waiting to run
Temporal Readiness / fast-readiness (push) Waiting to run
Temporal Readiness / docker-parity (push) Waiting to run
TypeScript Type Check / Nx affected typecheck (push) Waiting to run
Unit Tests / Skipped-test budget (push) Waiting to run
Unit Tests / Nx affected unit tests (push) Waiting to run
Unit Tests / Server unit coverage (informational) (push) Waiting to run
Validate Tenant Management Schema / Check for relevant changes (push) Waiting to run
Validate Tenant Management Schema / Validate Tenant Management Schema (push) Blocked by required conditions
EE Workflows Build Guard / ee-workflows-build-guard (push) Waiting to run
Excluded: .git, node_modules, secrets/, compose.env, assemblyscript tgz Source: /opt/alga-psa on psa.joliet.tech
34 lines
1.2 KiB
Markdown
34 lines
1.2 KiB
Markdown
# Workflow Fixture Harness (V1)
|
|
|
|
Runs a single workflow fixture end-to-end:
|
|
|
|
1) Import a workflow bundle (`bundle.json`)
|
|
2) Run the fixture trigger/assertions script (`test.cjs`)
|
|
3) Print a PASS/FAIL single-line summary (plus optional JSON)
|
|
|
|
Fixture root (Enterprise):
|
|
- `ee/test-data/workflow-harness/`
|
|
|
|
## Usage
|
|
|
|
```bash
|
|
node tools/workflow-harness/run.cjs \
|
|
--test ee/test-data/workflow-harness/ticket-created-hello \
|
|
--base-url http://localhost:3010 \
|
|
--tenant <tenantId> \
|
|
--cookie-file /path/to/cookie.txt \
|
|
--force
|
|
```
|
|
|
|
Notes:
|
|
- `--cookie` / `--cookie-file` should be the raw `Cookie` header value (e.g. `next-auth.session-token=...`).
|
|
- `--tenant` sets `x-tenant-id` so the server runs in the correct tenant context.
|
|
- If you don't have a session cookie, you can omit `--cookie*` and instead set `WORKFLOW_HARNESS_API_KEY` (or `ALGA_API_KEY`) so the harness injects `x-api-key` automatically.
|
|
- Prefer running with `--force` so fixtures are re-runnable (overwrites workflows by key).
|
|
- DB assertions require Postgres connectivity. Set `DATABASE_URL` or pass `--pg-url`.
|
|
|
|
## Fixture keys
|
|
|
|
Fixtures should use deterministic workflow keys:
|
|
- `fixture.<folderName>` (example: `fixture.ticket-created-hello`)
|