---
id: TST-PFM-DJE-026
title: Group dependencies
kind: integration
product_area: platform
module: data-job-engine
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
  services-membership: 5994c270e8a37a30f848e99ba5b5ee6b87c08893
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: macroservice-libraries
files:
  - packages/data-jobs/src/tests/integration/group-dependencies.integration.spec.ts
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  Suite-owned fixture records, job identifiers and workspace contexts; teardown removes the fixture
  data.
evidence:
  - >-
    macroservice-libraries:packages/data-jobs/src/tests/integration/group-dependencies.integration.spec.ts
assertion_inventory:
  - a group whose members name each other
  - >-
    applies the head office and its 39 branches in one pass when they share a group, whatever their
    order in the file
  - >-
    orders a chain of dependencies, so a grandchild listed first still lands after its parent and
    grandparent
  - 'still refuses the whole group when a member is rejected, and writes none of it'
  - >-
    blocks the group of a member that waits for an item of another group, and a retry after that
    item lands applies it
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Group dependencies

## Verification Boundary

The suite checks the production service or shared engine against its database fixture. The structured assertion inventory records the checks present at the pinned revision.

## What This Suite Proves

The existing checks exercise group dependencies. The specification bindings identify the narrower outcomes supported by those assertions.

## What It Does Not Prove

Local execution does not establish deployed queue, storage or service behavior. Independent test cases do not establish a complete cross-feature process.

## Real Dependencies and Test Doubles

The shared engine uses real Postgres with a test domain operation and repository. File suites use a fake object store; transport publication uses test ports.

## Must Not Be Doubled

The database effects, security context and production operation under examination remain real. Their outcomes cannot be replaced with canned success responses.