---
id: TST-COM-CAT-037
title: Stores Verification
kind: integration
product_area: commerce
module: catalog
revision: 1
status: draft
product_intent: proposed
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
repository: services-commerce
files:
  - modules/configuration/tests/integration/services/persistence/stores.integration.spec.js
implements:
  - ATS-COM-CAT-003-03
  - ATS-COM-CAT-003-04
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-03
    source: >-
      services-commerce:modules/configuration/tests/integration/services/persistence/stores.integration.spec.js#refuses
      another tenant’s category as unknown
  - scenario: ATS-COM-CAT-003-03
    source: >-
      services-commerce:modules/configuration/tests/integration/services/persistence/stores.integration.spec.js#refuses
      a home category outside an "only" rule’s categories, 400 naming home_category_id
  - scenario: ATS-COM-CAT-003-03
    source: >-
      services-commerce:modules/configuration/tests/integration/services/persistence/stores.integration.spec.js#refuses
      a home category an "all_but" rule leaves out, 400 naming home_category_id
  - scenario: ATS-COM-CAT-003-04
    source: >-
      services-commerce:modules/configuration/tests/integration/services/persistence/stores.integration.spec.js#refuses
      deleting a store a checkout was opened in, naming the store
evidence:
  - >-
    services-commerce:modules/configuration/tests/integration/services/persistence/stores.integration.spec.js
  - >-
    services-commerce:modules/configuration/tests/integration/services/persistence/stores.integration.spec.js#Real:
    PostgreSQL, the persistence services, the execution context and its transactions under
    `rhythm_commerce_app`.
  - >-
    services-commerce:modules/configuration/tests/integration/services/persistence/stores.integration.spec.js#Doubled:
    nothing.
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 suite calls the persistence, database or composed service layer against the integration database. It verifies committed rows and the refusals asserted by its cases.

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