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
22 lines
1.1 KiB
Markdown
22 lines
1.1 KiB
Markdown
# Workflow Harness Fixtures
|
|
|
|
Each fixture is a folder containing:
|
|
- `bundle.json` — a Workflow Bundle v1 (usually 1 workflow) with a deterministic `workflow.key` like `fixture.<name>`
|
|
- `test.cjs` — trigger + assertions script executed by `tools/workflow-harness/run.cjs`
|
|
|
|
## Conventions
|
|
|
|
- Folder name becomes the harness `testId` (e.g. `ticket-created-hello`).
|
|
- Workflow key should be `fixture.<folderName>`.
|
|
- Prefer `--force` imports so fixtures are re-runnable.
|
|
- Tests should register cleanup via `ctx.onCleanup(fn)` when they create domain records.
|
|
- Some fixtures trigger domain events via the REST API (`/api/v1/*`) which requires an API key. Set `WORKFLOW_HARNESS_API_KEY` (or `ALGA_API_KEY`) and pass it as `x-api-key` in `ctx.http.request(...)`.
|
|
|
|
## Naming scheme
|
|
|
|
Use a consistent, grep-friendly naming scheme:
|
|
- `<domain>-<event>-<behavior>` (examples: `ticket-created-hello`, `project-created-kickoff-tasks`, `invoice-overdue-reminder`)
|
|
|
|
Recommended domains:
|
|
- `ticket-*`, `project-*`, `invoice-*`, `payment-*`, `contract-*`, `appointment-*`, `schedule-*`, `company-*`, `time-*`
|