---
id: TST-PFM-INT-513
title: invalidation
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/invalidation.integration.spec.js
implements:
  - ATS-PFM-INT-004-07
  - ATS-PFM-INT-007-06
  - ATS-PFM-INT-007-07
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/invalidation.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#invalidates
      its active bindings with connection_suspended, at the next revision
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#tells
      the administrators once, after the commit, naming both bindings and why
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#restores
      them when it is resumed
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#sends
      no notice for the restoration
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#copies
      each change to the binding’s revisions
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#audits
      each change as binding.changed
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#writes
      each change to the security trail with the states either side (the setup bound through persistence,
      which audits nothing)
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#invalidates
      its bindings with connection_reauth_required
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#tells
      the administrators that the bindings can no longer run, beside the re-authorization notice
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#reports
      the lost feature, the premise
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#invalidates
      the binding that requires it with feature_lost
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#leaves
      the binding that requires nothing active
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#moves
      the pin, the premise
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#invalidates
      the dropped major’s binding with major_unsupported
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#leaves
      the binding of a major the new version implements active
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#invalidates
      the bindings of every connection under it, each connection having been suspended with it (the
      connection cause comes first)
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#restores
      them when it is resumed
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#is
      refused while an active binding chooses the connection, leaving the binding as it was
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#is
      refused while an invalid binding still points at the connection, leaving the binding as it was
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js#sends
      no notice
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/integrations/tests/integration/services/bindings/invalidation.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# invalidation

## Verification Boundary

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