---
id: TST-PFM-ELG-443
title: Eligibility bindings queries checks
kind: integration
product_area: platform
module: eligibility
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - >-
    modules/eligibility/tests/integration/services/persistence/bindings.queries.integration.spec.js
implements: []
environment: local
implementation_state: implemented
latest_result: not-run
conformance: not-verified
estimated_minutes: 5
isolation: Prepared local test database with suite-owned fixture keys and cleanup.
evidence:
  - provenance: test
    source: >-
      services-platform:modules/eligibility/tests/integration/services/persistence/bindings.queries.integration.spec.js
    cases:
      - maps every column of a binding
      - 'maps a following binding’s defaults, with no pin and no label'
      - answers nothing for a binding of another tenant
      - lists a definition’s bindings in id order
      - >-
        pages a definition’s bindings, the last page of exactly the size left
        carrying no cursor
      - lists a consumer application’s bindings in kind and record order
      - >-
        lists one consumer record’s bindings, and none of another tenant’s
        record of the same reference
      - >-
        pages a consumer application’s bindings in the same order, a cursor from
        one page opening the next (DEF-ELIG-0699)
      - >-
        pages a consumer kind’s bindings with the page as large as the rows
        left, carrying no cursor
      - >-
        lists the bindings of several records of a kind, paged by the keyset
        (PLAT-M11)
      - >-
        lists several records through the unpaged list too, and a record named
        once in both forms once
      - >-
        refuses more than 100 records, naming the limit, and several records
        without their kind
      - refuses a cursor this list did not return
      - >-
        narrows a definition’s bindings to a consumer application before the
        page is cut
      - answers an empty list for a consumer with no bindings
      - refuses a consumer record without its kind
      - >-
        counts a definition’s usage by consumer kind, with the active and pinned
        among them
      - counts no usage for a definition nothing binds
      - >-
        answers each definition’s bindings and active bindings, and nothing for
        one with none
      - answers nothing for another tenant’s definition
      - 'answers nothing for no definitions, without a statement'
      - >-
        answers the consumer kinds a definition is bound to, each once, in kind
        order
      - answers no consumer kind for a definition nobody binds
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/integration/services/persistence/bindings.queries.integration.spec.js:suite
      header
    note: >-
      The source header describes the verification boundary and declared
      substitutions.
proof_limit: >-
  No complete capability or feature scenario is mapped to this file; case-level
  ownership remains a coverage finding.
---

# Eligibility bindings queries checks

## Verification Boundary

This suite checks the module through real local service and database code at the entry points used by its test cases.

## What This Suite Proves

The file contains executable checks, but no complete scenario mapping is established here. Its source test titles identify the remaining mapping work.

## What It Does Not Prove

Registration supplies no execution result or conformance decision. Checks beyond the file’s reachable assertions remain unverified, including production configuration.

## Real Dependencies and Test Doubles

The suite uses local integration fixtures. Signing, caches, provider responses or outbound delivery may be supplied by fixtures where the source declares a substitution. The source imports and suite header identify the exact dependencies.

## Must Not Be Doubled

The module behavior under assertion, transaction boundary and database constraint being checked remain real. Fixture setup cannot stand in for the asserted write or refusal.