---
id: TST-COM-FUL-067
title: Staff movement keys
kind: unit
product_area: commerce
module: fulfillment
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-commerce
files:
  - modules/inventory/tests/unit/stock/staff-movement-keys.spec.js
implements:
  - ATS-COM-FUL-017-03
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/inventory/tests/unit/stock/staff-movement-keys.spec.js
    test_titles:
      - >-
        is the same movement when the retry restates the type, the quantity and the item by product,
        SKU and location
      - is the same movement when the retry names the item by id and leaves out the cost
      - >-
        is another movement when the key arrives with another SKU and quantity (the pads under the
        pens’ key)
      - is another movement when only the quantity differs
      - is another movement when only the type differs
      - is another movement when only the location differs
      - is another movement when the item id names another item
    scenario_anchors:
      - >-
        services-commerce:modules/inventory/tests/unit/stock/staff-movement-keys.spec.js#is the same
        movement when the retry restates the type, the quantity and the item by product, SKU and
        location
      - >-
        services-commerce:modules/inventory/tests/unit/stock/staff-movement-keys.spec.js#is another
        movement when the key arrives with another SKU and quantity (the pads under the pens’ key)
      - >-
        services-commerce:modules/inventory/tests/unit/stock/staff-movement-keys.spec.js#is another
        movement when only the quantity differs
---

# Staff movement keys

## Verification Boundary

This suite checks staff movement keys 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.