---
id: TST-COM-CAT-031
title: Stores Verification
kind: api-lifecycle
product_area: commerce
module: catalog
revision: 1
status: draft
product_intent: proposed
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
repository: services-commerce
files:
  - modules/configuration/tests/e2e/stores.e2e.spec.js
implements:
  - ATS-COM-CAT-003-01
  - ATS-COM-CAT-003-02
  - ATS-COM-CAT-003-05
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 2
isolation: 'Suite-owned workspace keys and database fixtures, removed by its cleanup hooks.'
binding_evidence:
  - scenario: ATS-COM-CAT-003-01
    source: >-
      services-commerce:modules/configuration/tests/e2e/stores.e2e.spec.js#answers 400 to a store
      without an ordering profile
  - scenario: ATS-COM-CAT-003-01
    source: >-
      services-commerce:modules/configuration/tests/e2e/stores.e2e.spec.js#answers 400 to an
      ordering profile the tenant does not have, naming the property
  - scenario: ATS-COM-CAT-003-02
    source: >-
      services-commerce:modules/configuration/tests/e2e/stores.e2e.spec.js#answers 400 to a currency
      or a business unit on the body: the store carries neither since D23
  - scenario: ATS-COM-CAT-003-05
    source: >-
      services-commerce:modules/configuration/tests/e2e/stores.e2e.spec.js#replaces a store at the
      version read, the purchasing roles with it, and answers 409 to the stale version after
evidence:
  - 'services-commerce:modules/configuration/tests/e2e/stores.e2e.spec.js'
  - >-
    services-commerce:modules/configuration/tests/e2e/stores.e2e.spec.js#Real: the composed handler,
    the routes, the mapper, the persistence services and PostgreSQL.
  - >-
    services-commerce:modules/configuration/tests/e2e/stores.e2e.spec.js#Doubled: the signing key
    pair. Every call acts in a tenant of the spec's own, registered in the local `platform.tenants`
    stand-in, emptied through the API and removed in `after`.
execution_constraints:
  - No execution is performed in this documentation back-fill.
verification_boundary: >-
  Bindings identify the existing assertions contributing to each scenario; several suites can
  jointly cover a compound scenario.
---

# Stores Verification

## Verification Boundary

The composed API handler runs locally with signed caller contexts and the integration database. Its route, mapping, permission and persistence assertions establish the local API boundary.

## What This Suite Proves

The stores assertions contribute to the scenarios listed in the register. Each binding retains its exact source test anchor so a reviewer can distinguish an individual contribution from the complete scenario.

## What It Does Not Prove

The register records source inspection only. It establishes no run result, delivery qualification or Product approval.

## Real Dependencies and Test Doubles

PostgreSQL and the services called by the suite are real. External service ports, file storage and queues may use the fixtures declared by the suite and its support helpers.

## Must Not Be Doubled

Keep the asserted database constraints, transactions, service functions and execution contexts real. For API suites, preserve the dispatcher and permission enforcement.