Skip to main content

Workflow Testing Architecture

Summary​

One Workflow-specific API smoke script exists and is included in the broader regression runner. No Workflow unit-test or integration-test project was found.

Testing architecture​

Existing smoke coverage​

The script verifies health/seed presence, two-stage definition authoring, publication, manager and role assignment, instance retrieval, advancement, completion, rejection, delegation, worklists, duplicate-decision conflicts and six outbox event types.

Coverage boundaries​

The smoke test requires a running service and persistence. It exercises public service behavior rather than isolated classes. The regression runner references the script.

Not implemented​

No verified unit coverage targets aggregates, conditions, mappings, repositories or result translation. No isolated integration fixture, authorization test, tenant-isolation test, concurrency test, failure-injection test or frontend Workflow test was found.

Recommended work includes aggregate transition tests, condition/operator cases, simultaneous decisions, authorization/tenant boundaries, outbox failure recovery and gateway/UI integration. These are recommendations, not current capability.

Requires Confirmation​

CI execution frequency, test-environment ownership and acceptance thresholds require confirmation.

Source References​

  • microservices/scripts/smoke-workflow.ps1
  • microservices/scripts/run-v1-regression.ps1
  • microservices/src/workflow-service/workflow-service.csproj
  • microservices/HrSuit.Microservices.sln

See Also​

Keywords​

Workflow architecture, approval engine, Workflow Service, technical foundation.

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Next review: 2026-10-20