--- id: TST-PFM-INT-510 title: binding migration 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-migration.integration.spec.js implements: - ATS-PFM-INT-007-09 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-migration.integration.spec.js test_cases: - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#answers what would be migrated, with no binding id provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#answers every refusal with its reason provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#writes nothing provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#migrates only the bindings of that scope kind provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#migrates the binding of the named connection and supersedes the source provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#records the source’s supersession as a revision migrated provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#leaves the sources of a run without it current, so callers of the old major still resolve provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#migrates what the earlier runs left and what is eligible provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#refuses each ineligible binding with its reason and leaves the already migrated one alone provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#answers every refusal with a detail naming what failed, without the error class provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#writes each migrated binding with the source’s scope, connection, features, policy and note, active at revision 1 provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#migrates a source that was invalid as an active binding when its connection is eligible provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#keeps the sources current provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#records each written binding’s first revision as migrated provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#writes a binding.changed audit row naming the majors provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#writes a security audit row of the binding provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#answers the bindings it migrated already_bound and migrates nothing provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#refuses a target major the contracts do not define provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#refuses migrating a major to itself provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#migrates 200 in the first call and counts the rest provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#migrates the rest in the second call, the first call’s bindings answering already_bound provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js#has nothing left to migrate in the third call provenance: test dependency_evidence: provenance: test source: >- services-platform:modules/integrations/tests/integration/services/bindings/binding-migration.integration.spec.js reviewed: - Suite introduction - Fixture setup - Client substitutions - Assertions and cleanup --- # binding migration ## Verification Boundary This database and service suite exercises binding migration. 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.