---
id: TST-COM-ORD-098
title: Amendments persistence
kind: integration
product_area: commerce
module: orders
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
repository: services-commerce
files:
  - modules/orders/tests/integration/services/persistence/amendments.queries.integration.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: The suite creates its own test workspace records and removes them using the fixture cleanup.
evidence:
  - provenance: test
    source: >-
      services-commerce:modules/orders/tests/integration/services/persistence/amendments.queries.integration.spec.js
    test_cases:
      - >-
        writes the document requested, numbered 10000, with its line planned and active, the effective date as
        given
      - >-
        refuses a second active request on the line, 409 line_already_amending (11 §8), and the empty or
        doubled request
      - >-
        answers the document by id, the order’s newest first, the amendment of its change order, the active
        lines and the lines by id; nothing of another tenant
      - >-
        records the plan, the net, the treatment and each line’s values; moves along 11 §4.2 and refuses a
        move it does not allow
      - >-
        marks a line executed with its new line, claims and fences, settles it, and ends the lines’ active
        flag with a terminal status
scenario_coverage: []
dependency_evidence:
  provenance: test
  source: >-
    services-commerce:modules/orders/tests/integration/services/persistence/amendments.queries.integration.spec.js
  declared_by_test: 'PostgreSQL, the persistence service, the execution context under `rhythm_commerce_app`. Doubled: nothing.'
---

# Amendments persistence

## Verification Boundary

The suite exercises persistence or workflow operations against the local integration database.

## What This Suite Proves

The registered cases check amendments persistence 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

PostgreSQL and the exercised Commerce persistence or workflow code are real. Remote service records, clocks and transports follow the suite’s fixtures.

## Must Not Be Doubled

The database constraints, role restrictions, locks and transactions exercised by this suite must use PostgreSQL.