Invocation relies on binding resolution, credential admission and later settlement. The interaction cases follow uncertain and asynchronous results through recovery, cancellation and event completion without assuming that a new account choice moves existing work.
The structured scenarios name the capabilities and rules involved. A bound test contributes only the outcomes it asserts; proposed transition matrices and composed interactions still require executable proof.
Coverage
Rulegap: FND-PFM-INT-068
Transitioncovered
Validationcovered
Permissioncovered
Edgecovered
Failurecovered
Boundarycovered
Concurrencycovered
Invariantcovered
Interactioncovered
Test Scenarios
19 scenarios proving CAP-PFM-INT-009; 10 bound to an existing test.
01Invalid calls leave no execution recordvalidationunitnegativetest
Authorize and inspect execution and attempt records.
Expected
The record retains its attempt, request fingerprint, safe summaries and binding; the adapter uses the execution identity and no credential is persisted.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Exercise pre-send timeout, retry-after, adapter error, decline and post-send timeout.
Expected
Pre-send failure retries, retry-after waits, adapter error retries once, decline returns immediately and post-send uncertainty is investigated rather than repeated.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Prepare one independent record in each starting state, including absent-record cases where the model defines creation.
Steps
Run each listed transition once with its guard satisfied, then repeat it with the guard denied. Inspect the resulting record and listed side effects after commit.
Expected
Each positive case reaches its listed destination and records its defined side effects. Each denied case preserves the starting record and creates no transition side effects.
Data
Run-owned records and principals in an isolated workspace.
Prepare one independent record in each starting state, including absent-record cases where the model defines creation.
Steps
Run each listed transition once with its guard satisfied, then repeat it with the guard denied. Inspect the resulting record and listed side effects after commit.
Expected
Each positive case reaches its listed destination and records its defined side effects. Each denied case preserves the starting record and creates no transition side effects.
Data
Run-owned records and principals in an isolated workspace.
A sensitive binding selects an account with an open circuit and another usable account exists.
Steps
Resolve and invoke the capability, then inspect the trace and adapter calls.
Expected
Resolution identifies the selected account and circuit condition; admission refuses without contacting either processor.
Data
Run-owned records and principals in an isolated workspace.
Source
services-platform:modules/integrations/tests/unit/services/binding-resolution.spec.ts#resolves a payment whose processor’s circuit is open rather than refusing it binding_ineligible,services-platform:modules/integrations/tests/integration/services/executions/invoke-capability.integration.spec.js#refuses with 503 provider_unavailable while the circuit is open, and releases the key