--- id: TST-PFM-INT-514 title: resolve 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/resolve.integration.spec.js implements: - ATS-PFM-INT-008-01 - ATS-PFM-INT-008-03 - ATS-PFM-INT-008-04 - ATS-PFM-INT-008-06 - ATS-PFM-INT-008-07 - ATS-PFM-INT-008-08 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/resolve.integration.spec.js test_cases: - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#resolves a tender on A at the resource, to Payrix provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#walks a tender on B, which has no resource binding, to its business unit and Stripe provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#refuses a third merchant account, in a business unit with no binding, with no_binding after every scope provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#refuses with exactly the contracts’ InvokeResult refusal provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#answers another tenant no_binding for the same merchant account provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#resolves a new payment on the account to Stripe, at the binding’s second revision provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#reaches the processor that took the payment through its named connection provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#refuses a disconnected processor with connection_disconnected provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#refuses a suspended processor with connection_unavailable provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#refuses a processor that needs re-authorization with connection_unavailable provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#refuses another tenant’s connection as one that is not there provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#answers a degraded named connection with the connection_degraded warning provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#resolves a connection whose pin implements the capability in the mode and is deployed provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#answers connection_unavailable for a capability the connection’s pin does not implement provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#answers connection_unavailable for a mode the pin does not implement provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#answers connection_unavailable when the pinned version has no deployment here provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#answers the named connection’s own refusals before the capability’s provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#is a 400 for a capability the contracts do not define provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#is a 400 for a major the contracts do not define provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#walks to the application’s account, which has webinars, warning that the resource binding was skipped provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#shows the skipped binding in the trace, missing webinar provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#resolves a meeting at the resource, which needs no webinar provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#resolves with the connection_degraded warning while the circuit is closed provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#still resolves the payment to its processor, never touching the application’s (admission answers the circuit) provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#records the open circuit under its check, which passes, so Explain still shows it provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#resolves again once the probe is due, the circuit then half-open provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#offers the connections with manual capture and not the one without provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#then resolves the merchant account to the connection chosen, at the resource binding’s first revision provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#run in a transaction that refuses any write provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#read the tenant’s rows afresh on every resolution: a suspension is seen at once provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#resolves before the change provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#keeps serving the cached version within 60 seconds provenance: test - source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#sees the retirement once the entry expires provenance: test dependency_evidence: provenance: test source: >- services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js reviewed: - Suite introduction - Fixture setup - Client substitutions - Assertions and cleanup --- # resolve ## Verification Boundary This database and service suite exercises resolve. 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.