---
id: TST-PFM-DJE-186
title: Data run services
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-run-services.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-run-services.spec.ts'
assertion_inventory:
  - 'DATA_RUN_SERVICES: the macroservices a run may ask to load a dataset'
  - 'declares the two a migration package names today, and no object type anywhere'
  - >-
    reaches Platform at Platform’s own host, so the run calls the macroservice rather than itself in
    process
  - 'knows nothing of a macroservice that has no entry, which is what makes a third one one line'
  - 'dataRunServiceEnvironment: the addresses a deployed driver carries'
  - sets Platform’s address to its development host
  - 'sets CRM’s address to its development host, by the same derivation'
  - sets one variable per declared service and nothing else
  - >-
    sets every service’s address in the variable the run reads for it, so the two halves cannot
    disagree
  - 'addresses every service over TLS, so no deployment can configure a plain-HTTP macroservice'
  - 'ends no address with a slash, because the port appends the object’s route to it'
  - keeps a host the stack already resolved to a URL from being addressed twice over
  - every object type prefix a package can name has an address
  - sends every data operation Platform performs on its own records to a declared service
  - 'sends a CRM dataset, which is most of a package, to a declared service'
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Data run services

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