---
id: TST-COM-CAT-121
title: Allocation Verification
kind: unit
product_area: commerce
module: catalog
revision: 1
status: draft
product_intent: proposed
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
repository: services-commerce
files:
  - modules/promotions/tests/unit/pricing/allocation.spec.js
implements:
  - ATS-COM-CAT-016-06
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: In-process fixtures; any shared port replacement is restored by the suite.
binding_evidence:
  - scenario: ATS-COM-CAT-016-06
    source: >-
      services-commerce:modules/promotions/tests/unit/pricing/allocation.spec.js#shares 3000 over
      10000, 5000 and 2500 as 1714, 857, 429: the largest fraction gets the unit
  - scenario: ATS-COM-CAT-016-06
    source: >-
      services-commerce:modules/promotions/tests/unit/pricing/allocation.spec.js#shares 2500 over
      three 10000 lines as 834, 833, 833: the tie goes to the first line
  - scenario: ATS-COM-CAT-016-06
    source: >-
      services-commerce:modules/promotions/tests/unit/pricing/allocation.spec.js#sums to the amount
      exactly, every part its floor or one more and never above its basis, ties to the earlier line
evidence:
  - 'services-commerce:modules/promotions/tests/unit/pricing/allocation.spec.js'
  - >-
    services-commerce:modules/promotions/tests/unit/pricing/allocation.spec.js#Real: the allocation
    functions and the shared allocator of `@rhythmsoftware/macroservice-money`.
  - 'services-commerce:modules/promotions/tests/unit/pricing/allocation.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.
---

# Allocation Verification

## Verification Boundary

The suite exercises the isolated rule, calculation or adapter with its supplied fixtures. It does not establish storage or distributed behaviour.

## What This Suite Proves

The allocation 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

The production function under test is real. Its collaborators are supplied as fixtures or replaced ports where the suite declares them.

## Must Not Be Doubled

Keep the production function under test and its refusal or arithmetic result real. Replacing that function with a fixture removes the claimed proof.