---
id: TST-COM-ORD-162
title: The refusal of a purchase order cancel
kind: unit
product_area: commerce
module: orders
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
repository: services-commerce
files:
  - modules/purchasing/tests/unit/orders/purchase-order-cancel.spec.js
implements:
  - ATS-COM-ORD-017-04
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: 'The suite owns its in-memory inputs, scripted responses and rendered component state.'
evidence:
  - provenance: test
    source: 'services-commerce:modules/purchasing/tests/unit/orders/purchase-order-cancel.spec.js'
    test_cases:
      - 'tells a partially received order to close instead, not its status'
      - tells a fully received order to close instead
      - cancels a draft and an issued order nothing was received against
      - 'names the status of a closed order, which can no longer be closed, though it received stock'
      - names the status of an order already cancelled
scenario_coverage:
  - scenario: ATS-COM-ORD-017-04
    test_cases:
      - 'tells a partially received order to close instead, not its status'
      - cancels a draft and an issued order nothing was received against
    scope: >-
      The cited cases exercise the scenario’s listed fixture outcomes; this register makes no verified
      conformance claim.
dependency_evidence:
  provenance: test
  source: 'services-commerce:modules/purchasing/tests/unit/orders/purchase-order-cancel.spec.js'
  declared_by_test: 'the rule. Doubled: the lines, literal quantities.'
---

# The refusal of a purchase order cancel

## Verification Boundary

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

## What This Suite Proves

The registered cases check the refusal of a purchase order cancel 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.