Rhythm 2.0 Specifications

Appearance

ATS-PFM-NOT-011Review workspace notification activity: Capability Test Specification

Markdown

ATS-PFM-NOT-011

Review workspace notification activity: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-NOT-011

Design

Executed by
TST-PFM-NOT-002, TST-PFM-NOT-003, TST-PFM-NOT-013, TST-PFM-NOT-014, TST-PFM-NOT-021, TST-PFM-NOT-069, TST-PFM-NOT-073, TST-PFM-NOT-094, TST-PFM-NOT-109

KindAcceptance test setProduct areaPlatformModuleStaff Notifications and Association CommunicationsRevision2

Read atservices-platform ad3f6a65react-console baf6dae3

Review workspace notification activity: Capability Test Specification ​

Coverage ​

Each scenario names the guarantee it proves. Category coverage describes specified cases; executable bindings retain their narrower assertion boundaries. Lifecycle coverage remains a gap wherever guards and effects lack independent verification.

RuleProof
BR-CAP-PFM-NOT-011-01ATS-PFM-NOT-011-01, ATS-PFM-NOT-011-07
BR-CAP-PFM-NOT-011-02ATS-PFM-NOT-011-02
BR-CAP-PFM-NOT-011-03ATS-PFM-NOT-011-03
BR-CAP-PFM-NOT-011-04ATS-PFM-NOT-011-04
BR-CAP-PFM-NOT-011-06ATS-PFM-NOT-011-05
BR-CAP-PFM-NOT-011-08FND-PFM-NOT-072

Prepare one accepted request and one request with an empty audience. Inspect both in administrator History and their diagnostic detail, then compare HQ History with and without an active workspace grant.

The interaction case combines the producing, processing and reading outcomes named in its frontmatter. It remains proposed until an executable suite performs that complete sequence.

Coverage

  • Rule gap: FND-PFM-NOT-072
  • Transition not-applicable
  • Validation covered
  • Permission covered
  • Edge covered
  • Failure gap: FND-PFM-NOT-072
  • Boundary covered
  • Concurrency gap: FND-PFM-NOT-072
  • Invariant gap: FND-PFM-NOT-072
  • Interaction covered

Test Scenarios

7 scenarios proving CAP-PFM-NOT-011; 6 bound to an existing test.

01 Require notification management for Historypermissionapinegativetest
Proves
BR-CAP-PFM-NOT-011-01
Preconditions
Prepare a administrator and a clerk with only the use permission.
Steps
Retrieve History, the requests list and a chain as each.
Expected
Administrator reads succeed; each equivalent clerk request is denied.
Data
Use only records created and owned by this suite.
Bound to
services-platform:modules/notifications/tests/e2e/notifications.e2e.spec.js#refuses History and the chain to a caller with only platform.notifications.use
services-platform:modules/notifications/tests/e2e/notifications.e2e.spec.js#leaves the list to an administrator, not to a caller who only reads their own
services-platform:modules/notifications/tests/unit/permissions.spec.js#puts manage at tier admin and sensitive, for the Administrator
Source
services-platform:modules/notifications/tests/e2e/notifications.e2e.spec.js#refuses History and the chain to a caller with only platform.notifications.use
02 Filter and page workspace Historyvalidationapitest
Proves
BR-CAP-PFM-NOT-011-02
Preconditions
Create several recipients' items spanning two monthly partitions.
Steps
Retrieve the list of History; narrow by each filter; page across the month boundary; send an unrecognized status.
Expected
Results match the selected filters in descending time order. Paging crosses months without lost records, and invalid status input fails.
Data
Use only records created and owned by this suite.
Bound to
services-platform:modules/notifications/tests/integration/services/centre/notification-centre.integration.spec.js#lists every person’s notifications newest first with the person and the request
services-platform:modules/notifications/tests/e2e/notifications.e2e.spec.js#lists every person’s notifications with the person, and narrows by filters
Source
services-platform:modules/notifications/tests/integration/services/centre/notification-centre.integration.spec.js#lists every person’s notifications newest first with the person and the request
03 Include requests that produced no noticesedgebrowsertest
Proves
BR-CAP-PFM-NOT-011-03
Preconditions
Prepare a request that excluded an outsider, an invalid one of 201 people and one that was heard.
Steps
Open History's Requests view; narrow by outcome.
Expected
All three requests show their outcomes and notice counts; the first problem is visible and diagnostic navigation opens.
Data
Use only records created and owned by this suite.
Bound to
services-platform:modules/notifications/tests/e2e/notifications.e2e.spec.js#lists a request that dropped a named person, one that was refused as invalid and one that was heard, and no other tenant’s
services-platform:modules/notifications/tests/e2e/notifications.e2e.spec.js#narrows by outcome, definition and since, newest first, and pages by keyset
services-platform:modules/notifications/tests/integration/services/persistence/requests.queries.integration.spec.js#maps every request with the number of instances it made, none for the ones that told nobody
react-console:components/notifications/__tests__/notifications.test.tsx#lists the requests that told nobody in the Requests view, with the first problem, and opens the chain on one
Source
services-platform:modules/notifications/tests/e2e/notifications.e2e.spec.js#lists a request that dropped a named person, one that was refused as invalid and one that was heard, and no other tenant’s
04 Read complete request, notice and delivery linksinteractionapitest
Proves
BR-CAP-PFM-NOT-011-04
Preconditions
Prepare a accepted request with one notice and its deliveries.
Steps
Retrieve the request, the notice and a delivery.
Expected
Each detail supplies its linked records, with empty collections represented as lists.
Data
Use only records created and owned by this suite.
Bound to
services-platform:modules/notifications/tests/integration/services/centre/notification-centre.integration.spec.js#carries the why and the deliveries of each notification on the request, as the notification’s own chain does
services-platform:modules/notifications/tests/e2e/notifications.e2e.spec.js#reads the request, the notification with its why and the delivery with its chain
react-console:components/notifications/__tests__/notifications.test.tsx#opens the chain on a request whose problems are null or absent (DEF-NT-0011)
Source
services-platform:modules/notifications/tests/integration/services/centre/notification-centre.integration.spec.js#reads a request with the notifications it made
05 Keep administrator reads inside the workspaceboundaryapinegativetest
Proves
BR-CAP-PFM-NOT-011-06
Preconditions
Two workspaces with notices.
Steps
Retrieve History and a chain of the other organization by id.
Expected
Other-workspace records are absent and direct foreign lookups return not found.
Data
Use only records created and owned by this suite.
Bound to
Source
services-platform:modules/notifications/tests/integration/services/centre/notification-centre.integration.spec.js#shows nothing of another tenant
06 Investigate delivered and recipient-less activityinteractionbrowsertest
Proves
AS-JNY-PFM-NOT-003-01 AS-JNY-PFM-NOT-003-02 AS-JNY-PFM-NOT-003-03
Preconditions
Create items for Jane and colleagues, an outsider-only request and an audience with two hundred and one candidates.
Steps
Exercise the administrator review workflow.
Expected
History exposes Jane's item, diagnostic chain and unused channels; request view includes both submissions that produced no notices.
Data
The journey's own personas and Northeast unit.
Bound to
Source
react-console:acceptance/notifications/playwright/journeys/history/NT-ACC-0100.spec.ts#NT-ACC-0100
07 Workspace investigation carries the same chain into granted supportinteractionapiproposed
Proves
BR-CAP-PFM-NOT-011-04
Preconditions
Prepare one accepted request and one request with an empty audience.
Steps
Inspect both in administrator History and their diagnostic detail, then compare HQ History with and without an active workspace grant.
Expected
The accepted request links its explained notice and deliveries; the empty request remains inspectable without notices. Granted HQ lists agree with administrator lists and ungranted reads refuse access.
Data
A suite-owned workspace, named staff accounts and unique occurrence keys; external adapters record attempts without shared writes.
Source
rhythm-v2-docs:specs/platform/notifications/planning/capabilities/CAP-PFM-NOT-011-see-what-the-organization-told-whom.md#frontmatter,rhythm-v2-docs:specs/platform/notifications/planning/capabilities/CAP-PFM-NOT-010-understand-why-i-was-told.md#frontmatter,rhythm-v2-docs:specs/platform/notifications/planning/capabilities/CAP-PFM-NOT-012-support-a-customers-notifications-from-rhythm-hq.md#frontmatter

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