---
id: TST-PFM-INT-466
title: extension bindings
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/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js
implements:
  - ATS-PFM-INT-017-05
  - ATS-PFM-INT-017-06
  - ATS-PFM-INT-017-07
  - ATS-PFM-INT-017-08
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/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#creates
      a draft at the tenant scope on the point’s current version, its empty scope id left off the record
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      a scope kind the point does not allow
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      a scope that names no record, or a tenant scope that names one
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      a handler that does not implement the point
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      a handler the tenant does not have
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      a failure policy the point does not allow
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      an overriding failure policy without a note, and accepts it with one
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      a deprecated version, and accepts a supported one
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      a point that is not registered
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      to create a binding orphaned
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      a second enabled binding at one scope as an IllegalOperation naming the scope
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      an effective window that ends before it starts
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#binds
      the rule on the version it fits
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      to bind the rule on a version it does not fit, naming the problems, and writes nothing
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      to move a rule’s binding onto a version it does not fit, leaving the row as it was
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#enables
      a draft, then puts it in shadow, then disables it, each at the version read
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      a move to orphaned, leaving the row as it was
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      a change at a stale version
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#refuses
      a change the validation rules refuse, leaving the row as it was
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#lets
      an orphaned binding be disabled and nothing else
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#does
      not find another tenant’s binding to change or delete
    provenance: test
  - source: >-
      services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js#deletes
      a binding, answering its id, and records every change in the security trail
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/extensions/tests/integration/services/persistence/extension-bindings.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# extension bindings

## Verification Boundary

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

## What This Suite Proves

The bindings identify the detailed outcomes asserted by this suite. Test-level evidence retains the individual checks, including cases where several suites contribute to one scenario.

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