---
id: TST-COM-FUL-055
title: Obligation queue
kind: unit
product_area: commerce
module: fulfillment
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-commerce
files:
  - modules/fulfillment/tests/unit/register/obligation-queue.spec.js
implements:
  - ATS-COM-FUL-004-01
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-memory inputs, recorded calls and test-owned doubles; no shared customer records.'
evidence:
  - repository: services-commerce
    path: modules/fulfillment/tests/unit/register/obligation-queue.spec.js
    test_titles:
      - >-
        is a pointer: the version, the tenant, the obligation and the authorization, and nothing of
        the row’s content
      - carries the correlation id when the row has one
      - 'is parsed back from its body, and a body of this version with every id is accepted'
      - >-
        refuses junk, another version, a missing id and a correlation id that is not text, as
        nothing to act on
      - >-
        keeps every item published, refuses the authorizations it was told to, and drains what it
        kept
      - >-
        refuses to be built with no queue URL in the environment, so a dispatcher cannot silently
        drop its rows
    scenario_anchors:
      - >-
        services-commerce:modules/fulfillment/tests/unit/register/obligation-queue.spec.js#is a
        pointer: the version, the tenant, the obligation and the authorization, and nothing of the
        row’s content
---

# Obligation queue

## Verification Boundary

This suite checks obligation queue with controlled inputs and recorded dependencies. Its entry points remain within the process.

## What This Suite Proves

The bound scenarios identify the assertions this suite contributes. Source anchors retain the exact test cases; where a capability scenario has several contributing suites, a single binding does not imply that every branch runs here.

## What It Does Not Prove

Controlled inputs do not establish database enforcement, deployed integration or browser behavior. A recorded call is evidence about the adapter contract rather than a remote operation.

## Real Dependencies and Test Doubles

The imported logic is real; test inputs and dependency responses are controlled. Queue publication uses the suite’s recording or scripted publisher.

## Must Not Be Doubled

Keep the imported production logic and its request construction real. Record dependency calls and refusals rather than replacing the behavior being asserted.