---
id: TST-PFM-INT-538
title: connection notices
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/executions/connection-notices.integration.spec.js
implements:
  - ATS-PFM-INT-004-09
  - ATS-PFM-INT-006-06
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/executions/connection-notices.integration.spec.js
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#records
      the warnings of a succeeded call with the setting, and the call is answered as it always was
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#counts
      a recurrence on the same row and moves last seen, keeping first seen and taking the latest message
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#records
      several codes of one call, each once, and the setting is optional
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#records
      nothing for a result without warnings, with an empty list, or that failed
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#reads
      warnings defensively: a malformed one is skipped, the rest kept, at most ten, and the payment still
      succeeded
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#a
      result carrying warnings is not an unknown outcome even where the bundled contracts predate the
      field
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#records
      the warnings of an accepted result too, and only of a succeeded or accepted one
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#writes
      nothing to the integration audit trail or the security trail when a notice is first recorded
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#cuts
      a message over 500 characters rather than failing the call
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#never
      throws when the notice cannot be stored: the call that succeeded stands
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#when
      the installation settings change, with the clearing recorded and the change audited as it always
      was
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#not
      when the settings are written unchanged, or when only the acceptance changes
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#only
      the installation’s own connections’ notices
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#when
      the connection’s configuration changes
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#when
      the connection is disconnected
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#and
      a call that warns again afterwards starts the notice afresh
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#clearing
      is idempotent and counts only what it cleared
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#stop
      showing without a recurrence, and restart on one
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#a
      recurrence inside the thirty days keeps a notice live past them
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js#the
      tenant list pages by connection then code, and is the tenant’s own
    provenance: test
dependency_evidence:
  provenance: test
  source: >-
    services-platform:modules/integrations/tests/integration/services/executions/connection-notices.integration.spec.js
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# connection notices

## Verification Boundary

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