---
id: TST-PFM-INT-484
title: connection try
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/connection-try.e2e.spec.js
implements:
  - ATS-PFM-INT-012-01
  - ATS-PFM-INT-012-02
  - ATS-PFM-INT-012-03
  - ATS-PFM-INT-012-04
  - ATS-PFM-INT-012-05
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/connection-try.e2e.spec.js'
test_cases:
  - source: >-
      services-platform:modules/integrations/tests/e2e/connection-try.e2e.spec.js#is answered 200 with
      the execution id and the gateway’s result
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/connection-try.e2e.spec.js#records an execution of
      that connection by the calling application library_try on behalf of the person, with no binding
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/connection-try.e2e.spec.js#uses a fresh
      idempotency key for each call, so two identical calls are two executions
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/connection-try.e2e.spec.js#writes a
      connection.test_call audit row naming the capability, the execution and the person
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/connection-try.e2e.spec.js#sees the connection’s
      account_environment in its GET
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/connection-try.e2e.spec.js#is refused 403 and no
      execution or audit row is recorded
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/connection-try.e2e.spec.js#is refused 409
      connection_not_test when the provider reported a live account, and no execution is recorded
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/connection-try.e2e.spec.js#is refused 409
      connection_not_test when the environment was never reported
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/connection-try.e2e.spec.js#is refused 409
      connection_unavailable when it is suspended
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/connection-try.e2e.spec.js#is refused 409
      capability_unsupported for a capability the connection is not verified for
    provenance: test
  - source: >-
      services-platform:modules/integrations/tests/e2e/connection-try.e2e.spec.js#is refused 404 for a
      connection the tenant does not have
    provenance: test
dependency_evidence:
  provenance: test
  source: 'services-platform:modules/integrations/tests/e2e/connection-try.e2e.spec.js'
  reviewed:
    - Suite introduction
    - Fixture setup
    - Client substitutions
    - Assertions and cleanup
---
# connection try

## Verification Boundary

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