---
id: TST-COM-CAT-061
title: Pricing Audiences 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/pricing-audiences.e2e.spec.js
implements:
  - ATS-COM-CAT-010-01
  - ATS-COM-CAT-010-02
  - ATS-COM-CAT-010-04
  - ATS-COM-CAT-010-06
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-01
    source: >-
      services-commerce:modules/pricing/tests/e2e/pricing-audiences.e2e.spec.js#lists standard for
      everyone at rank 0 and member by eligibility at rank 10, built in, member shown to visitors,
      with no binding yet
  - scenario: ATS-COM-CAT-010-01
    source: >-
      services-commerce:modules/pricing/tests/e2e/pricing-audiences.e2e.spec.js#renames a built-in
      and keeps it built in, and refuses it another kind, 409 audience_built_in
  - scenario: ATS-COM-CAT-010-01
    source: >-
      services-commerce:modules/pricing/tests/e2e/pricing-audiences.e2e.spec.js#deletes a tenant’s
      own audience, after which it reads 404; refuses a built-in’s delete, 409 audience_built_in
  - scenario: ATS-COM-CAT-010-02
    source: >-
      services-commerce:modules/pricing/tests/e2e/pricing-audiences.e2e.spec.js#answers 400 with the
      problem code audience_rank_taken to a rank another audience holds, creating nothing
  - scenario: ATS-COM-CAT-010-04
    source: >-
      services-commerce:modules/pricing/tests/e2e/pricing-audiences.e2e.spec.js#refuses the delete
      409 audience_in_use with the sentence and the details
  - scenario: ATS-COM-CAT-010-04
    source: >-
      services-commerce:modules/pricing/tests/e2e/pricing-audiences.e2e.spec.js#still deactivates
      the audience
  - scenario: ATS-COM-CAT-010-06
    source: >-
      services-commerce:modules/pricing/tests/e2e/pricing-audiences.e2e.spec.js#answers 409 to a
      stale version, 400 to a body whose id is not the path’s, and 400 to a replacement without its
      version
evidence:
  - 'services-commerce:modules/pricing/tests/e2e/pricing-audiences.e2e.spec.js'
  - >-
    services-commerce:modules/pricing/tests/e2e/pricing-audiences.e2e.spec.js#Real: the composed
    handler, the routes, the mapper, the persistence services and PostgreSQL.
  - >-
    services-commerce:modules/pricing/tests/e2e/pricing-audiences.e2e.spec.js#Doubled: the signing
    key pair.
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.
---

# Pricing Audiences 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 pricing audiences 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.