Rhythm 2.0 Specifications

Appearance

ATS-PFM-CSH-007Visit settings and return to the preceding work: Capability Test Specification

Markdown

ATS-PFM-CSH-007

Visit settings and return to the preceding work: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-CSH-007

Design

Executed by
TST-PFM-CSH-015, TST-PFM-CSH-019, TST-PFM-CSH-022

KindAcceptance test setProduct areaPlatformModuleConsole Shell and NavigationRevision3

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

Visit settings and return to the preceding work: 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-007-02ATS-PFM-CSH-007-01
BR-CAP-PFM-CSH-007-03ATS-PFM-CSH-003-05, ATS-PFM-CSH-007-02
BR-CAP-PFM-CSH-007-04ATS-PFM-CSH-007-03
BR-CAP-PFM-CSH-007-06ATS-PFM-CSH-007-04
BR-CAP-PFM-CSH-007-10ATS-PFM-CSH-007-06

Area offers need a permission matrix across all six areas and their destinations. Back to app needs both a remembered record and fresh direct entry; shortcut visibility must stay distinct from destination authorization.

The first session receives the overview refusal and the second can inspect application availability; area access supplies no substitute for the page key.

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-057
  • Validation gap: FND-PFM-CSH-057
  • Permission gap: FND-PFM-CSH-057
  • Edge gap: FND-PFM-CSH-057
  • Failure gap: FND-PFM-CSH-057
  • Boundary gap: FND-PFM-CSH-057
  • Concurrency gap: FND-PFM-CSH-057
  • Invariant gap: FND-PFM-CSH-057
  • Interaction gap: FND-PFM-CSH-057

Test Scenarios

7 scenarios proving CAP-PFM-CSH-007; 3 bound to an existing test.

01 Area offers require a readable destinationpermissionunitnegativetest
Proves
BR-CAP-PFM-CSH-007-02
Preconditions
Grant fixtures cover area access alone, one Security destination, full grants and no grants.
Steps
Calculate each fixture’s offered settings areas.
Expected
Area-only and empty fixtures offer nothing; the readable Security fixture offers Security and full grants offer the registered areas.
Data
Independent fixture inputs for the variants listed in this case.
Bound to
Source
react-console:lib/console/__tests__/settings-area-menu.test.ts#does not offer Security or Maintenance to a person who holds only the areas' access keys
02 Settings departure resumes the prior recordinteractionbrowserproposed
Proves
BR-CAP-PFM-CSH-007-03 AS-JNY-PFM-CSH-002-01 AS-JNY-PFM-CSH-002-03
Preconditions
An administrator starts on an existing record page.
Steps
Enter Configuration, visit Regions and select Back to app.
Expected
The settings menu replaces daily navigation; the return action restores the original record destination.
Data
An isolated browser context with the stated identity, workspace and response fixtures.
Source
react-console:components/console/app-sidebar.tsx:AppSidebar, SettingsNavigation
03 Administrative roots choose their recorded first pagerulebrowserproposed
Proves
BR-CAP-PFM-CSH-007-04
Preconditions
A permitted fixture can enter each administrative root.
Steps
Open Security, Maintenance and Data Management independently.
Expected
Their initial destinations are Users, Scheduled Jobs and Data Imports respectively.
Data
An isolated browser context with the stated identity, workspace and response fixtures.
Source
react-console:docs/url-architecture.md#4.1 Tenant console
04 Older Maintenance paths keep their view and queryinteractionunitproposed
Proves
BR-CAP-PFM-CSH-007-06
Preconditions
Compatibility fixtures name duplicate-rule and integration paths with suffixes and queries.
Steps
Resolve each former Maintenance destination.
Expected
The resulting Configuration address retains the requested suffix and query.
Data
Independent fixture inputs for the variants listed in this case.
Source
react-console:docs/url-architecture.md#3. Workspaces
05 Every Security menu entry reaches its destinationrulebrowsertest
Proves
BR-CAP-PFM-CSH-007-07
Preconditions
The development administrator holds the required Security grants.
Steps
Enter Security through the account menu and select every registered area.
Expected
Every selected entry reaches its recorded destination and visible heading.
Data
An isolated browser context with the stated identity, workspace and response fixtures.
Bound to
Source
react-console:e2e/security/navigation.spec.ts#reaches every Security area from the sidebar
06 Orders settings expose Stores without Price Schedulesruleunittest
Proves
BR-CAP-PFM-CSH-007-10
Preconditions
The Orders settings menu and configuration catalogue are inspected together.
Steps
Find Stores and inspect both catalogues for Price Schedules.
Expected
Stores carries its own view grant; neither catalogue contains Price Schedules.
Data
Independent fixture inputs for the variants listed in this case.
Bound to
Source
react-console:lib/console/__tests__/orders-nav.test.ts
07 Configuration entry hands off to the application overview guardinteractionbrowserproposed
Proves
BR-CAP-PFM-CSH-007-01 BR-CAP-PFM-CSH-017-01
Preconditions
A user can enter Configuration but lacks application-view authority.
Steps
Open Configuration home directly, then repeat with the view key.
Expected
The first session receives the overview refusal and the second can inspect application availability; area access supplies no substitute for the page key.
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-007-move-into-a-settings-area-and-back-to-my-work.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