---
id: TST-PFM-ELG-428
title: Eligibility consumer bindings 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/bindings/consumer-bindings.integration.spec.js
implements:
  - ATS-PFM-ELG-007-02
  - ATS-PFM-ELG-007-05
  - ATS-PFM-ELG-007-07
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/bindings/consumer-bindings.integration.spec.js
    cases:
      - >-
        stores the binding following the published version, active, with the
        consumer it names
      - >-
        takes the consumer kind’s default fail policy when the request names
        none
      - records the create in the audit trail
      - pins a version named by its number
      - accepts the parameters the rule declares
      - 'refuses a consumer kind the registry does not have, and writes nothing'
      - refuses a kind of another application than the binding’s
      - refuses a rule that needs a subject the kind does not supply
      - refuses a type that cannot run in batch for a population kind
      - refuses a function type for a kind that decides in SQL only
      - refuses a required parameter left out
      - refuses a version number the definition does not have
      - refuses a new binding of a deprecated definition
      - >-
        refuses a change to parameters the rule does not declare, and leaves the
        binding as it was
      - 'changes the parameters at the version read, and records it'
      - refuses a change at a version that is no longer current
      - 'removes a binding, records it, and finds it no more'
      - lists a definition’s bindings
      - narrows a definition’s bindings to one consumer record
      - lists one consumer record’s bindings across definitions
      - lists nothing of this tenant’s for another tenant
      - refuses a list that names neither a definition nor a consumer
  - provenance: documented
    source: >-
      services-platform:modules/eligibility/tests/integration/services/bindings/consumer-bindings.integration.spec.js:suite
      header
    note: >-
      The source header describes the verification boundary and declared
      substitutions.
proof_limit: >-
  Only the named scenario checkpoints have a verified source binding; execution
  has not been attempted.
---

# Eligibility consumer bindings 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 mapped scenarios identify the capability and feature checkpoints this file exercises. The source test titles preserve the assertion-level evidence.

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