---
id: TST-PFM-INT-555
title: integration bindings queries
kind: integration
product_area: platform
module: integrations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-platform
files:
  - >-
    modules/integrations/tests/integration/services/persistence/integration-bindings.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: 5
isolation: >-
  Use the suite-owned database fixtures and its declared cleanup; prepare the test database before
  integration or lifecycle execution.
evidence:
  - >-
    services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      the active binding at a scope, every field mapped
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      an invalid binding with its reason, since an invalid binding is still current
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      the binding that replaced another, never the superseded one
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      nothing at a scope nothing is bound at
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      another tenant its own binding at the colliding scope
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      the current bindings in id order by default, none superseded and none of another tenant
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#filters
      by scope kind
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#filters
      by scope reference
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      the superseded ones when the status names them
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      nothing for a capability nothing binds
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#pages
      by id: a full first page with the next key, and the rest without one
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#ends
      an exactly full last page without a next key
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      its current bindings in id order
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#includes
      an invalid one and leaves out the one it lost to a replacement
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#counts
      only the active ones
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#counts
      the invalid ones with the active ones as current
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#pages
      its current bindings, invalid included, by the limit
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      every copy, oldest first, each mapped whole
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      one revision by its number
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      nothing for a revision the binding never had
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      another tenant none of the tenant’s revisions
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      every revision of every row of the scope, newest first, from either row’s id
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      each revision’s stored snapshot, unchanged
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      who changed it and when, each by shape
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#pages
      with a keyset: a first page with the next key, then the rest with none
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#ends
      an exactly full last page without a next key
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#leaves
      out the revisions of another scope
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      not found for a binding the tenant does not have
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js#answers
      another tenant not found for the tenant’s binding
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/integrations/tests/integration/services/persistence/integration-bindings.queries.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# integration bindings queries

## Verification Boundary

This database and service suite exercises integration bindings queries. Its registration records the executable definition; no run result is asserted.

## What This Suite Proves

The suite contains executable checks, but no detailed scenario binding is verified in this pass.

## What It Does Not Prove

In-process execution does not establish deployed infrastructure or a real provider response. Several bindings can supply different parts of a detailed scenario; no single-file completeness is implied.

## Real Dependencies and Test Doubles

The suite definition identifies its database fixtures and replaced clients, hooks, clocks or executors. Integration runs use the prepared database; lifecycle runs exercise the in-process route or adapter path.

## Must Not Be Doubled

The database constraints, transactions and service behavior claimed by an integration binding must execute. Replaced external seams cannot establish live provider or infrastructure behavior.