---
id: TST-COM-CAT-066
title: Member Pricing Tables 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/pricing/tests/integration/db/member-pricing-tables.table.integration.spec.js
implements:
  - ATS-COM-CAT-010-03
  - ATS-COM-CAT-011-01
  - ATS-COM-CAT-011-03
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-010-03
    source: >-
      services-commerce:modules/pricing/tests/integration/db/member-pricing-tables.table.integration.spec.js#refuses
      an operation audience without an operation, and operations on another kind, by
      pricing_audiences_operations_check
  - scenario: ATS-COM-CAT-010-03
    source: >-
      services-commerce:modules/pricing/tests/integration/db/member-pricing-tables.table.integration.spec.js#refuses
      a binding on an audience that is not an eligibility one, by pricing_audiences_binding_check
  - scenario: ATS-COM-CAT-011-01
    source: >-
      services-commerce:modules/pricing/tests/integration/db/member-pricing-tables.table.integration.spec.js#holds
      no owner column (COMM-M1 D2), and refuses a blank zone, which the text-normalization trigger
      makes null, by the NOT NULL
  - scenario: ATS-COM-CAT-011-03
    source: >-
      services-commerce:modules/pricing/tests/integration/db/member-pricing-tables.table.integration.spec.js#records
      the first sale once, never cleared or moved, after which the period keeps its name and is
      never deleted, nor its schedule
evidence:
  - >-
    services-commerce:modules/pricing/tests/integration/db/member-pricing-tables.table.integration.spec.js
  - >-
    services-commerce:modules/pricing/tests/integration/db/member-pricing-tables.table.integration.spec.js#Real:
    PostgreSQL built from the migrations, both roles as the bootstrap makes them, the execution
    context's transaction and its session settings.
  - >-
    services-commerce:modules/pricing/tests/integration/db/member-pricing-tables.table.integration.spec.js#Doubled:
    nothing. Never doubled: the role switch, the tenant setting, the triggers or row-level security.
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.
---

# Member Pricing Tables 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 member pricing tables 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.