---
id: TST-PFM-DJE-107
title: Bulk data jobs
kind: api-lifecycle
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/e2e/bulk-data-jobs.e2e.spec.js
implements:
  - ATS-PFM-DJE-014-01
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/e2e/bulk-data-jobs.e2e.spec.js'
assertion_inventory:
  - bulk data jobs API (end to end)
  - a producer submitting the file it has uploaded
  - accepts the submission and names the job it made
  - 'answers the bulk lane, queued, because nobody has read the file yet'
  - >-
    is read through its own collection’s job route, which every lane shares, with nothing counted
    yet
  - who may import organizations from a file
  - 'refuses an unsigned call with 401, because importing a file is nobody’s by default'
  - refuses a context that does not cover the tenant in the path with 403
  - refuses a caller who may update one organization but holds no bulk key with 403
  - a submission naming a file it may not read
  - 'refuses an upload of another tenant with 400, saying only that it was not found'
  - >-
    refuses an upload id of no upload at all in the same words, so neither answer tells a caller
    whose it is
  - 'refuses an upload whose file has not arrived with 400, naming the state it is in'
  - >-
    refuses a body that names a bucket and a key with 400, because a caller names an upload and
    nothing else
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Bulk data jobs

## Verification Boundary

The suite checks requests through the local production dispatcher and signed caller evaluation. The structured assertion inventory records the checks present at the pinned revision.

## What This Suite Proves

The existing checks exercise bulk data jobs. 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.