---
id: TST-PFM-INT-489
title: integrations
kind: api-lifecycle
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/e2e/integrations.e2e.spec.js
implements:
  - ATS-PFM-INT-001-10
  - ATS-PFM-INT-002-05
  - ATS-PFM-INT-004-01
  - ATS-PFM-INT-004-02
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/e2e/integrations.e2e.spec.js'
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#finds the integration in
      the catalog
    provenance: test
  - source: 'services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#installs it, enabled'
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#connects a platform
      account, which starts verifying with its job
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#answers the connection
      the string id its name derives to
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#discovers the connection
      once it is active with the feature verified, and answers no credential
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#is told a platform
      account has nothing to re-authorize, with 409
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#reads the tenant’s audit
      trail of the connection
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#is refused Rhythm HQ’s
      catalog (403)
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#derives the id from the
      name when none is given
    provenance: test
  - source: 'services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#uses an explicit id'
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#refuses an id outside the
      grammar, 400 naming the field
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#refuses a second
      connection of the tenant whose name derives to a taken id, 409 naming the id
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#accepts that name with an
      explicit id
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#is refused the catalog
      (403)
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#is refused the tenant’s
      connections (403)
    provenance: test
  - source: 'services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#reads Rhythm HQ’s catalog'
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js#answers its health
      without a caller
    provenance: test
dependency_evidence:
  provenance: test
  source: 'services-platform:modules/integrations/tests/e2e/integrations.e2e.spec.js'
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# integrations

## Verification Boundary

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