---
id: TST-PFM-DJE-181
title: Data job call
kind: unit
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-platform
files:
  - modules/data-jobs/tests/unit/data-job-call.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: 1
isolation: In-memory fixtures and restored dependency doubles.
evidence:
  - 'services-platform:modules/data-jobs/tests/unit/data-job-call.spec.ts'
assertion_inventory:
  - the call a Data Run step makes to the owning macroservice
  - submits to the owning service’s own data-job route under the address its environment names
  - >-
    sends exactly the owning service’s bulk-lane body: no object type, no mode, the dataset as the
    delivery id
  - 'refuses to submit a file-backed job for a validate run, which the bulk lane cannot honour'
  - appends the route to an address configured with a trailing slash rather than doubling it
  - 'carries the staff caller’s own token as a bearer token, which is the only identity a run has'
  - asks for JSON and says it is sending JSON when it sends a body
  - 'says nothing about a content type on a read, which sends no body'
  - >-
    names the dataset’s upload and the producer whose keys its lines carry, which a keyed load
    cannot be submitted without
  - >-
    carries the execution’s correlation id, so the owning service’s log of the job continues this
    chain
  - 'gives the service a bounded time to answer, so a silent one cannot spend the whole request'
  - fails the call naming the service and the time it was given when nothing answers at all
  - >-
    refuses to call a service this environment gives no address for, naming the variable that would
    say
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Data job call

## Verification Boundary

The suite checks an isolated production calculation, declaration or adapter. The structured assertion inventory records the checks present at the pinned revision.

## What This Suite Proves

The existing checks exercise data job call. The specification bindings identify the narrower outcomes supported by those assertions.

## What It Does Not Prove

An isolated check does not establish a deployed workflow, database enforcement or complete feature acceptance.

## Real Dependencies and Test Doubles

The production function or declaration is exercised with in-memory inputs and dependency doubles. This boundary does not require a live database.

## Must Not Be Doubled

The production function under examination and its returned decisions remain real; replacing their answers defeats the check.