---
id: TST-PFM-DJE-005
title: Batch plan
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: macroservice-libraries
files:
  - packages/data-jobs/src/batch-plan.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:
  - 'macroservice-libraries:packages/data-jobs/src/batch-plan.spec.ts'
assertion_inventory:
  - planning a data job into batches
  - cuts items with no group into ranges of the batch size
  - 'answers one batch for a job smaller than one batch, carrying every item'
  - gives the last batch the remainder rather than padding it
  - 'covers every item exactly once, in order, with no gap between the ranges'
  - 'answers nothing for no items, so a job with an empty input plans no batch'
  - keeps a group whole by holding the batch open past its size
  - closes a batch at the end of a group that ends exactly on the boundary
  - holds the batch open for a group whose items are scattered through the input
  - 'never leaves a group divided between two batches, whatever the batch size'
  - plans a single batch when one group covers the whole input
  - 'refuses a batch size that is not a positive whole number, which would plan nothing or forever'
  - uses the default batch size of 25 when the caller names none
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Batch plan

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