---
id: TST-COM-CAT-064
title: Product Extensions 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/product-extensions.e2e.spec.js
implements:
  - ATS-COM-CAT-012-04
  - ATS-COM-CAT-012-05
  - ATS-COM-CAT-012-07
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-012-04
    source: >-
      services-commerce:modules/pricing/tests/e2e/product-extensions.e2e.spec.js#adds the function’s
      $2.50 to the next quote: $20.00 price row and $2.50 extension, $22.50
  - scenario: ATS-COM-CAT-012-04
    source: >-
      services-commerce:modules/pricing/tests/e2e/product-extensions.e2e.spec.js#keeps the row and
      ignores it when it is put inactive: back to $20.00
  - scenario: ATS-COM-CAT-012-04
    source: >-
      services-commerce:modules/pricing/tests/e2e/product-extensions.e2e.spec.js#removes the row,
      and the quote is at the price row again
  - scenario: ATS-COM-CAT-012-05
    source: >-
      services-commerce:modules/pricing/tests/e2e/product-extensions.e2e.spec.js#refuses a body
      naming another product
  - scenario: ATS-COM-CAT-012-05
    source: >-
      services-commerce:modules/pricing/tests/e2e/product-extensions.e2e.spec.js#refuses an unknown
      property such as a timeout, which belongs to the handler
  - scenario: ATS-COM-CAT-012-05
    source: >-
      services-commerce:modules/pricing/tests/e2e/product-extensions.e2e.spec.js#refuses a body
      without an extension_id
  - scenario: ATS-COM-CAT-012-07
    source: >-
      services-commerce:modules/pricing/tests/e2e/product-extensions.e2e.spec.js#lets a read-only
      principal read, and refuses it the PUT and the DELETE, 403 permission_missing
evidence:
  - 'services-commerce:modules/pricing/tests/e2e/product-extensions.e2e.spec.js'
  - >-
    services-commerce:modules/pricing/tests/e2e/product-extensions.e2e.spec.js#Real: the composed
    handler, the routes, the quote workflow, the engine, the extension persistence and PostgreSQL.
  - >-
    services-commerce:modules/pricing/tests/e2e/product-extensions.e2e.spec.js#Doubled: the signing
    key pair; the quote ports and the extension handlers (the fixtures the deployed route uses); the
    other services' tables.
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.
---

# Product Extensions 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 product extensions 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.