---
id: TST-COM-FUL-042
title: Obligations queries
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/persistence/obligations.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: 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/persistence/obligations.queries.integration.spec.js
    test_titles:
      - 'answers the obligation whole, every column mapped, a null one left out'
      - >-
        lists the waiting obligations depending on a line (M5), none once they wait no more, none
        for another line or tenant
      - lists an order’s obligations by line then unit
      - 'lists a participant’s obligations in the states asked, and none for no state'
      - never answers another tenant’s obligation
      - >-
        getObligationByAuthorization answers the obligation whose current authorization is named,
        and nothing for another tenant or an unknown id
      - >-
        listObligationsOfOrderLines answers the lines named, by line then unit, and nothing for no
        line
      - >-
        listPendingObligationsOfScope answers the pending obligations of a product, of an ordering
        profile, or of the tenant, with the line’s product and the order’s profile
      - >-
        the sweep’s reads answer references across tenants, oldest first: the stale pending
        obligations of ACCEPTED orders, and the in-flight ones past their deadline
      - refuses the sweep’s reads inside another transaction
    scenario_anchors: []
---

# Obligations queries

## Verification Boundary

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

## What This Suite Proves

The suite’s source cases exercise the registered boundary, but this back-fill does not map them to a complete capability or feature scenario. The executable record remains useful without an invented scenario binding.

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