---
id: TST-PFM-INT-511
title: binding move
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-move.integration.spec.js
implements:
  - ATS-PFM-INT-007-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/integrations/tests/integration/services/bindings/binding-move.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-move.integration.spec.js#replaces
      every active binding of the source with one choosing the target, at the same scope, policy and note
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-move.integration.spec.js#leaves
      the source with no active binding, so its disconnection is no longer refused
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-move.integration.spec.js#shows
      the move in each binding’s history as a replacement, the old binding superseded
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-move.integration.spec.js#audits
      each move, naming the connection it left and the one it reached
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-move.integration.spec.js#moves
      to another integration’s connection that serves the capability, the compatible case
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-move.integration.spec.js#refuses
      a binding whose required feature the target has not verified, leaving it on the source, and moves
      the rest
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-move.integration.spec.js#refuses
      every binding when the target is not active, moving nothing
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-move.integration.spec.js#writes
      nothing on a dry run, answering what would move
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-move.integration.spec.js#refuses
      to move a connection’s bindings to itself
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-move.integration.spec.js#refuses
      a target the workspace does not have
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-move.integration.spec.js#refuses
      a source the workspace does not have
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/binding-move.integration.spec.js#answers
      an empty move when the source has no active binding left
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/integrations/tests/integration/services/bindings/binding-move.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# binding move

## Verification Boundary

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