---
id: TST-PFM-DJE-192
title: Run summary
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/run-summary.spec.ts
implements:
  - ATS-PFM-DJE-016-10
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/run-summary.spec.ts'
assertion_inventory:
  - 'data runs: the summary of a run'
  - 'answers the run, its package and the instants it ran between'
  - answers each dataset with the four counts its own service reported
  - adds the datasets up into the run’s own totals
  - names no failure for a run that did not fail
  - 'data runs: the readiness verdict'
  - is ready when the run succeeded and every record of every dataset is accounted for
  - is not ready while the run is still running
  - 'is not ready for a failed run, and carries the failure the run recorded'
  - is not ready for a cancelled run
  - 'is not ready after a validation run, however well it went, because it wrote nothing'
  - names each dataset that failed
  - >-
    is not ready while records the domain rejected are unresolved, and says how many of which
    dataset
  - is not ready while records nothing could attempt are blocked
  - is not ready when a dataset’s counts do not add up to what the producer claimed
  - >-
    counts no records missing for a dataset the run never attempted, which the run itself already
    explains
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Run summary

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