Rhythm 2.0 Specifications

Appearance

ATS-PFM-CSH-005Find personal actions and support in the user menu: Capability Test Specification

Markdown

ATS-PFM-CSH-005

Find personal actions and support in the user menu: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-CSH-005

KindAcceptance test setProduct areaPlatformModuleConsole Shell and NavigationRevision3

Read atreact-console baf6dae3services-platform ad3f6a65rhythm-v2-docs 25e253cb

Find personal actions and support in the user menu: Capability Test Specification ​

Coverage ​

The coverage map describes specified proof, not a passing run. Each mandatory rule below has a scenario or an explicit finding; a proposed scenario remains an execution obligation even when its expected outcome follows the pinned implementation.

Mandatory RuleScenarios or Finding
BR-CAP-PFM-CSH-005-01ATS-PFM-CSH-005-01
BR-CAP-PFM-CSH-005-02ATS-PFM-CSH-005-02, ATS-PFM-CSH-005-05
BR-CAP-PFM-CSH-005-04ATS-PFM-CSH-005-03
BR-CAP-PFM-CSH-005-08ATS-PFM-CSH-005-04

Personal-menu coverage needs display-name and initials cases, sign-out delegation, staff-mode transitions and feedback’s rating and text limits. A local acknowledgement establishes no durable feedback receipt.

Settings and permitted responsibilities belong to workspace mode; HQ does not retain those workspace menu actions.

The interaction rows cite the contracts they exercise. Related combinations without a complete case remain in the coverage finding, together with cross-capability workflows and permission boundaries. A helper assertion is bound only for its stated outcome; the full browser handoff remains proposed until a suite checks it.

Pinned source and exact test anchors are recorded in frontmatter. Test bindings record static assertion review and use the executable-suite register; no product test result is inferred from that review. The prior planning and design examinations supply context, while this continuation records the remaining proof obligations explicitly.

Coverage

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

Test Scenarios

5 scenarios proving CAP-PFM-CSH-005; 0 bound to an existing test.

01 Personal identity selects a readable name and initialsruleunitproposed
Proves
BR-CAP-PFM-CSH-005-01
Preconditions
Account fixtures provide a display name, separate name parts or email alone.
Steps
Render the personal menu for each identity fixture.
Expected
The selected name, corresponding initials and email follow the identity fallback policy.
Data
Independent fixture inputs for the variants listed in this case.
Source
react-console:components/console/app-sidebar.tsx:initialsOf
02 Responsibilities depend on mode and read authoritypermissionbrowsernegativeproposed
Proves
BR-CAP-PFM-CSH-005-02
Preconditions
Fixtures cover an authorized workspace, a workspace without the grant and HQ.
Steps
Inspect the personal actions in each fixture.
Expected
Only the authorized workspace fixture includes My Responsibilities.
Data
An isolated browser context with the stated identity, workspace and response fixtures.
Source
react-console:components/console/app-sidebar.tsx:AppSidebar
03 Feedback thanks do not imply service receiptrulebrowserproposed
Proves
BR-CAP-PFM-CSH-005-04
Preconditions
A fresh feedback dialog is open with request capture enabled.
Steps
Select a rating and submit the dialog.
Expected
The local acknowledgement appears while no feedback submission request is sent.
Data
An isolated browser context with the stated identity, workspace and response fixtures.
Source
react-console:components/console/feedback-dialog.tsx:FeedbackDialog
04 Feedback validates selection and text lengthvalidationbrowsernegativeproposed
Proves
BR-CAP-PFM-CSH-005-08
Preconditions
No rating is selected when the dialog opens.
Steps
Try submission, choose a rating and enter more than the supported details length.
Expected
Submission requires the rating; the details control accepts no more than 2,000 characters.
Data
An isolated browser context with the stated identity, workspace and response fixtures.
Source
react-console:components/console/feedback-dialog.tsx:FeedbackDialog
05 Personal actions follow the staff working modeinteractionbrowserproposed
Proves
BR-CAP-PFM-CSH-005-02 BR-CAP-PFM-CSH-013-05
Preconditions
A staff user can enter an association workspace and HQ.
Steps
Inspect personal actions in the workspace, then return to HQ.
Expected
Settings and permitted responsibilities belong to workspace mode; HQ does not retain those workspace menu actions.
Data
A fresh browser context, isolated account fixtures and controlled responses for the listed transitions.
Source
rhythm-v2-docs:specs/platform/console-shell/planning/capabilities/CAP-PFM-CSH-005-reach-my-own-pages-help-and-sign-out-from-the-user-menu.md

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