---
id: TST-COM-FUL-006
title: Configuration imports
kind: integration
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/integration/services/operations/configuration-imports.integration.spec.js
implements:
  - ATS-COM-FUL-020-07
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/data-operations/tests/integration/services/operations/configuration-imports.integration.spec.js
    test_titles:
      - >-
        creates the ordering profile under the id its line names, through the profile persistence,
        the first of the tenant its default
      - >-
        creates the two well-formed stores and refuses the nameless one as its own invalid value, in
        one batch
      - >-
        unpacks a first-slice catalog document onto the store’s assortment columns (D-C-14), as the
        store API would take them
      - 'updates a store a second delivery of its key names, by the id the first wrote'
      - 'writes the crosswalk once per key, pointing at the record the key became'
      - >-
        reads a load back by its keys, each store exactly as its GET answers it, the keys nothing
        loaded missing, in the order asked
      - 'answers nothing for the same keys in another tenant: the crosswalk is the tenant’s own'
    scenario_anchors:
      - >-
        services-commerce:modules/data-operations/tests/integration/services/operations/configuration-imports.integration.spec.js#reads
        a load back by its keys, each store exactly as its GET answers it, the keys nothing loaded
        missing, in the order asked
      - >-
        services-commerce:modules/data-operations/tests/integration/services/operations/configuration-imports.integration.spec.js#answers
        nothing for the same keys in another tenant: the crosswalk is the tenant’s own
---

# Configuration imports

## Verification Boundary

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

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

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.