---
id: TST-COM-FUL-016
title: Import values
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/import-values.spec.js
implements: []
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/import-values.spec.js
    test_titles:
      - accepts the line the tool carries
      - 'refuses a property the contract does not name, at its path'
      - >-
        refuses an order without lines, an id that is not a UUIDv7, and money that is not whole
        minor units
      - 'refuses a line whose kind, state or fulfilment is not in the vocabulary'
      - names links and lines and nothing else
      - 'carries its codes nested, each with its 1.0 id, and refuses a code without one'
      - >-
        refuses a currency that is not three capitals and a benefit that is not a positive whole
        number
      - 'is always applied, with at least one allocation'
    scenario_anchors: []
---

# Import values

## Verification Boundary

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

## What This Suite Proves

The suite’s source cases exercise the registered boundary, but this back-fill does not map them to a complete capability or feature scenario. The executable record remains useful without an invented scenario binding.

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