---
id: TST-PFM-DJE-145
title: Organization update
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-crm
files:
  - modules/data-jobs/tests/unit/services/operations/organization-update.spec.js
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-crm:modules/data-jobs/tests/unit/services/operations/organization-update.spec.js'
assertion_inventory:
  - the organization update operation
  - what a submission and a record need
  - 'is registered beside the contact update, for the object type of organizations'
  - requires the bulk key and the update key of the organizations to submit
  - re-checks the update key for each record
  - names organizations by id or by the producer’s key
  - how it is put back
  - 'declares a rollback that compensates with the same update, written for contract version 1'
  - 'declares no rollback for an insert, as a contact import declares none'
  - what a patch may set
  - sets the organization’s own scalar fields in a rollback
  - 'leaves out the identity, the system columns, the derived columns and the lists in a rollback'
  - accepts a patch of an own field and of the custom field map
  - >-
    keeps only the fields a patch names, so a default is never written over what the organization
    holds
  - 'refuses a patch of the address list, naming it'
  - 'refuses a patch of a system column, naming it'
  - 'declares the same paths to the engine, the custom field map as one wildcard'
registration_note: Registration describes existing source; the suite is not executed by this documentation job.
---

# Organization update

## 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 organization update. 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.