---
id: TST-PFM-DJE-010
title: Collection columns
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/collection-columns.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/collection-columns.spec.ts'
assertion_inventory:
  - collection mapping targets
  - 'offers the preferred slot and every typed slot of every collection, for every field'
  - 'reads a target path as its collection, slot and field, and nothing else as one'
  - 'refuses at load time a type named preferred, or a field declared twice'
  - folding a spreadsheet row into collections
  - >-
    imports the commonest spreadsheet (name, e-mail, phone, address) with a usable preferred e-mail,
    phone and address
  - >-
    maps duplicate typed columns to one element each, the first declared type preferred when none is
    named
  - 'keeps a preferred value apart from typed ones, and makes it the typed one when it repeats it'
  - 'leaves a collection whose cells are all empty out of the record, so a patch never erases it'
  - >-
    names a column it cannot use rather than dropping it: an unknown target, a duplicate, a
    collection given twice
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Collection columns

## 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 collection columns. 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.