---
id: TST-COM-FUL-014
title: Data operations
kind: unit
product_area: commerce
module: fulfillment
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-commerce
files:
  - modules/data-operations/tests/unit/operations/data-operations.spec.js
implements:
  - ATS-COM-FUL-020-01
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: 'In-memory inputs, recorded calls and test-owned doubles; no shared customer records.'
evidence:
  - repository: services-commerce
    path: modules/data-operations/tests/unit/operations/data-operations.spec.js
    test_titles:
      - 'holds the twenty-five operations, keyed by object type and operation'
      - serves the twelve object types of the migration
      - 'finds an operation by its pair, and nothing for a pair nobody declares'
      - refuses a pair nobody declares by name
      - resolves a job to its operation
      - >-
        declares, for each collection, the bulk key a submission needs and the per-record key it
        re-checks
      - >-
        declares the datasets an order and a redemption depend on: the configuration before the
        orders, the orders and the promotions before the usages
      - 'accepts contract version 1 alone, everywhere'
    scenario_anchors:
      - >-
        services-commerce:modules/data-operations/tests/unit/operations/data-operations.spec.js#declares,
        for each collection, the bulk key a submission needs and the per-record key it re-checks
---

# Data operations

## Verification Boundary

This suite checks data operations with controlled inputs and recorded dependencies. Its entry points remain within the process.

## What This Suite Proves

The bound scenarios identify the assertions this suite contributes. Source anchors retain the exact test cases; where a capability scenario has several contributing suites, a single binding does not imply that every branch runs here.

## What It Does Not Prove

Controlled inputs do not establish database enforcement, deployed integration or browser behavior. A recorded call is evidence about the adapter contract rather than a remote operation.

## Real Dependencies and Test Doubles

The imported logic is real; test inputs and dependency responses are controlled.

## Must Not Be Doubled

Keep the imported production logic and its request construction real. Record dependency calls and refusals rather than replacing the behavior being asserted.