---
id: TST-COM-FUL-044
title: Obligation dispatcher
kind: integration
product_area: commerce
module: fulfillment
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-commerce
files:
  - >-
    modules/fulfillment/tests/integration/services/register/obligation-dispatcher.integration.spec.js
implements:
  - ATS-COM-FUL-004-01
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: >-
  Run-created workspace identifiers and fixture records in the prepared test database; concurrency
  cases own their extra connections.
evidence:
  - repository: services-commerce
    path: >-
      modules/fulfillment/tests/integration/services/register/obligation-dispatcher.integration.spec.js
    test_titles:
      - leaves every row for the next run
      - >-
        claims the three rows of both tenants, publishes a pointer for each, and reports the refused
        one
      - deletes the accepted rows and leaves the refused one
      - 'publishes the refused one on the next run once the queue accepts it, then finds nothing'
    scenario_anchors:
      - >-
        services-commerce:modules/fulfillment/tests/integration/services/register/obligation-dispatcher.integration.spec.js#claims
        the three rows of both tenants, publishes a pointer for each, and reports the refused one
      - >-
        services-commerce:modules/fulfillment/tests/integration/services/register/obligation-dispatcher.integration.spec.js#deletes
        the accepted rows and leaves the refused one
      - >-
        services-commerce:modules/fulfillment/tests/integration/services/register/obligation-dispatcher.integration.spec.js#leaves
        every row for the next run
---

# Obligation dispatcher

## Verification Boundary

This suite checks obligation dispatcher against the prepared PostgreSQL database. Its entry points are the persistence and service functions used by the tests.

## 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

Direct service and persistence calls do not establish the full HTTP permission contract, deployed scheduling or browser behavior. No execution result is claimed by this register.

## Real Dependencies and Test Doubles

The database and imported Commerce persistence services are real. Fixtures create the records owned by this run. Queue publication uses the suite’s recording or scripted publisher. Time-sensitive cases use a controlled clock where the source fixture supplies one.

## Must Not Be Doubled

Keep the database constraints, row visibility and persistence writes real when claiming this integration coverage. A canned repository response cannot replace the boundary being checked.