---
id: TST-PFM-INT-512
title: binding operations
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/bindings/binding-operations.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/bindings/binding-operations.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-operations.integration.spec.js#audits
      the creation with no state before it
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-operations.integration.spec.js#audits
      the replacement naming the binding and connection it superseded
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-operations.integration.spec.js#audits
      the removal as the binding superseded
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-operations.integration.spec.js#writes
      the creation, the replacement and the removal to the security trail
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-operations.integration.spec.js#names
      the connection and scope a binding chose in the security trail
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-operations.integration.spec.js#answers
      the removed binding superseded
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-operations.integration.spec.js#is
      a service principal’s own when the body names none
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-operations.integration.spec.js#refuses
      a service principal binding another application’s resource
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-operations.integration.spec.js#refuses
      a service principal that names an application other than its own
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-operations.integration.spec.js#refuses
      a console caller naming an application that does not own the resource
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/integrations/tests/integration/services/bindings/binding-operations.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# binding operations

## Verification Boundary

This database and service suite exercises binding operations. 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.