The proration model (11 §5)

Verification Boundary

The unit suite checks the named contract or helper with controlled inputs.

What This Suite Proves

The registered cases check the proration model (11 §5) with their fixture records and assertions. Scenario bindings name only the examples those cases exercise.

What It Does Not Prove

A registered file supplies no run result or verified conformance by itself. Local fixtures do not establish deployed cross-service behavior or complete browser journeys.

Real Dependencies and Test Doubles

Inputs and external responses are controlled in process; this suite establishes no deployed service behavior.

Must Not Be Doubled

The named contract validation or component behavior under assertion must use its actual implementation.

Show evidence (sources, provenance, origins, pinned commits)

Isolation: The suite owns its in-memory inputs, scripted responses and rendered component state.
Kind: unit
Repository: services-commerce
Environment: mock
Implementation state: implemented
Latest result: not-run
Conformance: not-verified

Test Files

services-commerce:modules/orders/tests/unit/amendments/proration.spec.js

Implements

ATS-COM-ORD-015-10

Implementation

The proration model (11 §5) ​

Verification Boundary ​

What This Suite Proves ​

What It Does Not Prove ​

Real Dependencies and Test Doubles ​

Must Not Be Doubled ​