Rhythm 2.0 Specifications

Appearance

ATS-PFM-INT-012Exercise a provider capability on a test account: Capability Test Specification

Markdown

ATS-PFM-INT-012

Exercise a provider capability on a test account: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-INT-012

Design

Executed by
TST-PFM-INT-340, TST-PFM-INT-484, TST-PFM-INT-516

KindAcceptance test setProduct areaPlatformModuleIntegration access, customer extensions and shared workflow configurationRevision3

Read atservices-platform ad3f6a65macroservice-libraries 54536a44react-console baf6dae3

Exercise a provider capability on a test account: Capability Test Specification ​

Coverage ​

RuleProved By
BR-CAP-PFM-INT-012-01ATS-PFM-INT-012-01
BR-CAP-PFM-INT-012-02ATS-PFM-INT-012-02
BR-CAP-PFM-INT-012-03ATS-PFM-INT-012-03
BR-CAP-PFM-INT-012-04ATS-PFM-INT-012-04, ATS-PFM-INT-012-07, ATS-PFM-INT-012-08
BR-CAP-PFM-INT-012-05ATS-PFM-INT-012-05
BR-CAP-PFM-INT-012-06ATS-PFM-INT-012-06
BR-CAP-PFM-INT-012-07FND-PFM-INT-074

Test calls share routing and admission with normal invocation, but use a test connection. The interaction cases inspect both the preview and recorded execution, including permission and environment restrictions.

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

  • Rule gap: FND-PFM-INT-074
  • Transition gap: FND-PFM-INT-074
  • Validation covered
  • Permission covered
  • Edge covered
  • Failure gap: FND-PFM-INT-074
  • Boundary gap: FND-PFM-INT-074
  • Concurrency gap: FND-PFM-INT-074
  • Invariant covered
  • Interaction covered

Test Scenarios

8 scenarios proving CAP-PFM-INT-012; 6 bound to an existing test.

01 Account environment gates test invocationvalidationapinegativetest
Proves
BR-CAP-PFM-INT-012-01
Preconditions
Prepare provider-reported test, live and unknown accounts.
Steps
Attempt a Library test call on each.
Expected
Only the test account executes; the others refuse before recording.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Bound to
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
02 Existing manager authority controls Try a callpermissionapinegativetest
Proves
BR-CAP-PFM-INT-012-02
Preconditions
Prepare a reader and integration manager.
Steps
Invoke a test operation as each.
Expected
The reader is refused without records and the manager proceeds.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Bound to
Source
services-platform:modules/integrations/tests/e2e/connection-try.e2e.spec.js#is refused 403 and no execution or audit row is recorded
03 Usability and capability support remain requiredvalidationapinegativetest
Proves
BR-CAP-PFM-INT-012-03
Preconditions
A test account is suspended and another lacks the requested feature.
Steps
Attempt the test operation against each.
Expected
The first reports unavailable and the second unsupported.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Bound to
Source
services-platform:modules/integrations/tests/e2e/connection-try.e2e.spec.js#is refused 409 connection_unavailable when it is suspended
04 Library testing retains ordinary gateway historyinteractionbrowsertest
Proves
BR-CAP-PFM-INT-012-04 AS-JNY-PFM-INT-003-02
Preconditions
An active test account is connected.
Steps
Open Try a call and authorize the same test amount twice.
Expected
Two separate executions use that connection without a binding, identify the person through the Library application and appear in Activity.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Bound to
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
05 Test initiation has a connection-history entryinvariantapitest
Proves
BR-CAP-PFM-INT-012-05
Preconditions
A test account is eligible.
Steps
Invoke from the Library and read connection history.
Expected
The entry identifies the capability, resulting execution and initiating person.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Bound to
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
06 Provider reports replace account classificationedgeapitest
Proves
BR-CAP-PFM-INT-012-06
Preconditions
Account descriptions return test, then live, and separately an invalid or absent report.
Steps
Verify each description.
Expected
Valid reports replace classification; other reports leave it unknown while verification can still succeed.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Bound to
Source
services-platform:modules/integrations/tests/integration/services/connections/connection-account-environment.integration.spec.js#records test when the provider reports a test account
07 A direct test uses its named accountinteractionapiproposed
Proves
BR-CAP-PFM-INT-008-08 BR-CAP-PFM-INT-012-04
Preconditions
A provider-reported test account supports the requested capability and has no binding.
Steps
Invoke through the Library and inspect resolution and execution identity.
Expected
The test uses that account directly and retains ordinary gateway history.
Data
Run-owned records and principals in an isolated workspace.
Source
services-platform:modules/integrations/tests/integration/services/bindings/resolve.integration.spec.js#reaches the processor that took the payment through its named connection,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
08 Library calls retain ordinary execution evidenceinteractionapiproposed
Proves
BR-CAP-PFM-INT-009-04 BR-CAP-PFM-INT-012-04
Preconditions
An active test account is usable from connection detail.
Steps
Invoke the same example twice through the Library and inspect Activity and account history.
Expected
Separate executions identify the person and selected account without requiring a binding.
Data
Run-owned records and principals in an isolated workspace.
Source
services-platform:modules/integrations/tests/integration/services/executions/invoke-capability.integration.spec.js#records the execution succeeded, with its digest, summaries, reference and one attempt,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

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software