---
id: TST-COM-CAT-055
title: Member Pricing Scenarios 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/pricing/tests/e2e/member-pricing-scenarios.e2e.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: 2
isolation: 'Suite-owned workspace keys and database fixtures, removed by its cleanup hooks.'
binding_evidence: []
evidence:
  - 'services-commerce:modules/pricing/tests/e2e/member-pricing-scenarios.e2e.spec.js'
  - >-
    services-commerce:modules/pricing/tests/e2e/member-pricing-scenarios.e2e.spec.js#Real: the
    composed handler, the routes, the quote workflow, the engine, the audiences and schedules
    persistence, the checkout persistence and PostgreSQL.
  - >-
    services-commerce:modules/pricing/tests/e2e/member-pricing-scenarios.e2e.spec.js#Doubled: the
    signing key pair; the ports (the fixtures the deployed route uses); the other services' tables
    (local stand-ins).
execution_constraints:
  - No execution is performed in this documentation back-fill.
verification_boundary: No full ATS or FAS scenario is bound after source inspection.
---

# Member Pricing Scenarios 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 member pricing scenarios checks supply engineering evidence without a complete specification scenario binding. Their existence does not imply scenario coverage.

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