Rhythm 2.0 Specifications

Appearance

ATS-PFM-INT-002Explore the integrations available to a workspace: Capability Test Specification

Markdown

ATS-PFM-INT-002

Explore the integrations available to a workspace: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-INT-002

Design

Executed by
TST-PFM-INT-015, TST-PFM-INT-107, TST-PFM-INT-344, TST-PFM-INT-345, TST-PFM-INT-390, TST-PFM-INT-391, TST-PFM-INT-437, TST-PFM-INT-454, TST-PFM-INT-455, TST-PFM-INT-489, TST-PFM-INT-490, TST-PFM-INT-515, TST-PFM-INT-552

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

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

Explore the integrations available to a workspace: Capability Test Specification ​

Coverage ​

RuleProved By
BR-CAP-PFM-INT-002-01ATS-PFM-INT-002-01
BR-CAP-PFM-INT-002-02ATS-PFM-INT-002-02
BR-CAP-PFM-INT-002-03ATS-PFM-INT-002-03
BR-CAP-PFM-INT-002-05ATS-PFM-INT-002-04, ATS-PFM-INT-002-06
BR-CAP-PFM-INT-002-06ATS-PFM-INT-002-05

Discovery supplies the release detail an administrator reviews before installation. The interaction case checks that the selected access survives that handoff and remains inspectable after adoption.

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 covered
  • Transition gap: FND-PFM-INT-054
  • Validation gap: FND-PFM-INT-054
  • Permission covered
  • Edge covered
  • Failure gap: FND-PFM-INT-054
  • Boundary gap: FND-PFM-INT-054
  • Concurrency gap: FND-PFM-INT-054
  • Invariant gap: FND-PFM-INT-054
  • Interaction covered

Test Scenarios

6 scenarios proving CAP-PFM-INT-002; 5 bound to an existing test.

01 Catalogue audience follows availabilityruleapitest
Proves
BR-CAP-PFM-INT-002-01
Preconditions
Use public, restricted, internal, inactive and unpublished integrations across two workspaces.
Steps
Read both catalogues as customer staff and as Rhythm staff in workspace context.
Expected
Public offers appear to both, restricted offers only to the granted workspace, internal offers only to Rhythm staff, and inactive or unpublished offers to neither.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Bound to
Source
services-platform:modules/integrations/tests/integration/services/catalog/catalog.integration.spec.js#shows a restricted integration only to the tenant granted it
02 Hidden offers look absent at every entryedgebrowsernegativetest
Proves
BR-CAP-PFM-INT-002-02
Preconditions
A provider is restricted to a different workspace.
Steps
Search for it and open its direct detail address.
Expected
Search omits the provider and direct navigation returns not found.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Bound to
Source
services-platform:modules/integrations/tests/integration/services/catalog/catalog.integration.spec.js#answers no detail for an integration the tenant may not see
03 Provider detail supports an informed installationrulebrowsertest
Proves
BR-CAP-PFM-INT-002-03
Preconditions
The test provider is published and available.
Steps
Open its catalogue card and inspect the detail tabs.
Expected
Overview, capability, access and release information matches the published declaration and identifies the current release.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Bound to
Source
services-platform:modules/integrations/tests/integration/services/catalog/catalog.integration.spec.js#answers the contracts the version implements, with their schemas and feature meanings
04 Availability changes preserve existing workspace recordsinteractionapitest
Proves
BR-CAP-PFM-INT-002-05
Preconditions
An existing installation and account connection remain after an offer is restricted away.
Steps
Read provider detail, installation detail, connection detail and their lists.
Expected
Provider detail returns not found while the workspace’s saved records remain readable.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Bound to
Source
services-platform:modules/integrations/tests/integration/services/installations/narrowed-availability.integration.spec.js#stays readable to the tenant that holds it: the installation, the connection and their lists answer, and the catalog entry stays hidden
05 Read-only access is useful without mutation controlspermissionbrowsernegativetest
Proves
BR-CAP-PFM-INT-002-06 AS-JNY-PFM-INT-001-04
Preconditions
Prepare a reader, manager and person without integration permissions.
Steps
Visit the Library, catalogue and account detail as each person.
Expected
The reader can inspect the screens without edit controls; the unauthorized person receives the access-denied explanation.
Data
Fixtures establishing the stated accounts, declarations and history in an isolated workspace.
Bound to
Source
react-console:lib/integrations/access.test.ts#shows a reader every screen, with no change control and no secret
06 Hidden offers preserve an existing adoptioninteractionapiproposed
Proves
BR-CAP-PFM-INT-002-05 BR-CAP-PFM-INT-003-01
Preconditions
One workspace already has an installation before its offer is restricted away.
Steps
Read the saved installation and attempt a fresh installation from an ungranted workspace.
Expected
Saved configuration remains readable while new adoption is refused.
Data
Run-owned records and principals in an isolated workspace.
Source
services-platform:modules/integrations/tests/integration/services/installations/narrowed-availability.integration.spec.js#stays readable to the tenant that holds it: the installation, the connection and their lists answer, and the catalog entry stays hidden,services-platform:modules/integrations/tests/integration/services/installations/installation-lifecycle.integration.spec.js#refuses an integration installed already, and writes no second

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