---
id: TST-PFM-INT-521
title: connection version update
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/connections/connection-version-update.integration.spec.js
implements:
  - ATS-PFM-INT-004-10
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/connections/connection-version-update.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/integration/services/connections/connection-version-update.integration.spec.js#INT-ACC-0115
      (a): a version the connection is already pinned to is refused 409 naming it (d: starts no job) and
      keeps the pin
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/connections/connection-version-update.integration.spec.js#INT-ACC-0115
      (b): a version of another integration is refused 400 as not a version of this one (d: starts no
      job) and keeps the pin
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/connections/connection-version-update.integration.spec.js#INT-ACC-0115
      (c, d): a suspended connection is refused 409 naming suspended, starts no job and keeps the pin
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/connections/connection-version-update.integration.spec.js#INT-ACC-0115
      (e): a version whose account differs keeps the pin and the connected account, outcome pin_kept, and
      says why
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/connections/connection-version-update.integration.spec.js#INT-ACC-0115
      (e): audits connection.version_update_failed carrying the reason and the version kept
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/connections/connection-version-update.integration.spec.js#INT-ACC-0115
      (f): once the account is fixed the same update moves the pin, outcome pin_moved, audited as
      version_updated
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/connections/connection-version-update.integration.spec.js#INT-ACC-0115
      (f): the fixed update reports pin_moved when verified directly
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/integrations/tests/integration/services/connections/connection-version-update.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# connection version update

## Verification Boundary

This database and service suite exercises connection version update. 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.