Skip to content

Testing Workflows

Test workflows before promotion to production.

Test Levels

  • Syntax validation for YAML files.
  • Local execution tests against the dev stack.
  • Integration tests with real downstream services.
  • Regression tests for critical business flows.

Practical Test Sequence

  1. Validate YAML and schema (workflow + bound triggers + schedules/connections as needed).
  2. Run representative payloads via one of:
  3. Trigger path — POST /v1/api/... from gateway_public_path (preferred public path).
  4. Dashboard — workflow / trigger example payloads.
  5. Orchestrator — POST /run/{workflow_name} (internal).
  6. Confirm expected step outputs and side effects.
  7. Inspect traces for branching/retry behavior.
  8. Validate failure paths and compensation behavior.

Do not rely only on gateway POST /v1/run/* — that alias is legacy/dev and may be disabled.

Suggested Checks

  • Happy path execution.
  • Missing header or invalid auth path (when gateway_auth_mode / policies require it).
  • Dependency failure and retry handling.
  • Idempotency behavior for repeated requests.
  • Schedule ticks when enabled: true (or manual scheduled invoke in lab).

Useful Endpoints

  • GET /v1/traces
  • GET /v1/traces/{request_id}
  • GET /api/trigger-events
  • Orchestrator GET /workflows