---
id: TST-COM-FUL-061
title: Inventory transfers queries
kind: integration
product_area: commerce
module: fulfillment
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-commerce
files:
  - >-
    modules/inventory/tests/integration/services/persistence/inventory-transfers.queries.integration.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: 3
isolation: >-
  Run-created workspace identifiers and fixture records in the prepared test database; concurrency
  cases own their extra connections.
evidence:
  - repository: services-commerce
    path: >-
      modules/inventory/tests/integration/services/persistence/inventory-transfers.queries.integration.spec.js
    test_titles:
      - 'lists the tenant’s transfers newest first, each half joined to the other'
      - 'pages the list: a limit of two answers the two newest and says there are more'
      - 'finds a transfer by the request’s key, and nothing for a key never used'
      - >-
        never answers another tenant’s transfer: the other tenant lists its one, under the same key
        as this tenant’s first
    scenario_anchors: []
---

# Inventory transfers queries

## Verification Boundary

This suite checks inventory transfers queries against the prepared PostgreSQL database. Its entry points are the persistence and service functions used by the tests.

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

Direct service and persistence calls do not establish the full HTTP permission contract, deployed scheduling or browser behavior. No execution result is claimed by this register.

## Real Dependencies and Test Doubles

The database and imported Commerce persistence services are real. Fixtures create the records owned by this run.

## Must Not Be Doubled

Keep the database constraints, row visibility and persistence writes real when claiming this integration coverage. A canned repository response cannot replace the boundary being checked.