---
id: TST-PFM-DJE-112
title: Bulk admission
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: services-crm
files:
  - modules/data-jobs/tests/integration/services/jobs/bulk-admission.integration.spec.js
implements:
  - ATS-PFM-DJE-014-05
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:
  - >-
    services-crm:modules/data-jobs/tests/integration/services/jobs/bulk-admission.integration.spec.js
assertion_inventory:
  - admitting two tenants’ bulk jobs in turn under one ceiling
  - 'plans four batches for each tenant’s job, so each could fill the tenant’s ceiling of three alone'
  - >-
    admits two batches to the first tenant, leaving the rest of the room to the second tenant
    waiting beside it
  - admits two batches to the second tenant in its turn
  - admits nothing more to the first tenant once the two tenants hold the whole ceiling
  - leaves each tenant holding two batches of the ceiling’s four
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Bulk admission

## 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 bulk admission. 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 owning service exercises production persistence and domain behavior against real Postgres. The fixture supplies caller contexts; queue delivery, storage and external calls are doubled where the file installs a test port.

## 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.