Rhythm 2.0 Specifications

Appearance

ATS-PFM-CSH-004Begin work from the workspace home: Capability Test Specification

Markdown

ATS-PFM-CSH-004

Begin work from the workspace home: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-CSH-004

Design

Executed by
TST-PFM-CSH-004, TST-PFM-CSH-014

KindAcceptance test setProduct areaPlatformModuleConsole Shell and NavigationRevision3

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

Begin work from the workspace home: 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-004-02ATS-PFM-CSH-004-02
BR-CAP-PFM-CSH-004-04ATS-PFM-CSH-004-01, ATS-PFM-CSH-004-06
BR-CAP-PFM-CSH-004-06ATS-PFM-CSH-004-04
BR-CAP-PFM-CSH-004-07ATS-PFM-CSH-004-03
BR-CAP-PFM-CSH-004-08ATS-PFM-CSH-004-05

Home coverage must distinguish live suppression from demonstration data, keep attention independent of dashboard readiness and inspect the zero-denominator presentation. Dashboard ownership remains a product question.

The landing and compatible home link use the established customer workspace rather than HQ.

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

Test Scenarios

6 scenarios proving CAP-PFM-CSH-004; 2 bound to an existing test.

01 Customer root entry selects the remembered workspacerulebrowsertest
Proves
BR-CAP-PFM-CSH-004-04 AS-JNY-PFM-CSH-001-02 AS-JNY-PFM-CSH-004-03
Preconditions
A customer session retains a reachable workspace choice.
Steps
Open the bare console address.
Expected
The chosen workspace home becomes the working destination.
Data
An isolated browser context with the stated identity, workspace and response fixtures.
Bound to
Source
react-console:e2e/mock/url-architecture.mock.spec.ts#the bare root opens the remembered tenant's home
02 Dashboard failure leaves attention work mountedfailurebrowsernegativeproposed
Proves
BR-CAP-PFM-CSH-004-02
Preconditions
Attention data is usable while the dashboard summary fails.
Steps
Open workspace home with the failed summary response.
Expected
Attention remains visible alongside the dashboard’s failure presentation.
Data
An isolated browser context with the stated identity, workspace and response fixtures.
Source
react-console:app/(console)/console/[tenantId]/page.tsx:HomePage
03 Dashboard explanations separate three unavailable statesvalidationunitnegativetest
Proves
BR-CAP-PFM-CSH-004-07
Preconditions
Inputs represent a missing service, actual request failure and missing configuration.
Steps
Render the dashboard error presentation for each fixture.
Expected
Each fixture receives the explanation appropriate to its condition.
Data
Independent fixture inputs for the variants listed in this case.
Bound to
Source
react-console:components/console/home/__tests__/dashboard-state.test.tsx
04 Live home omits the demonstration summary readboundarybrowserproposed
Proves
BR-CAP-PFM-CSH-004-06
Preconditions
Live and demonstration contexts are inspected separately.
Steps
Open home in both modes and capture summary requests.
Expected
Live home issues no summary request; demonstration home reads its sample summary.
Data
An isolated browser context with the stated identity, workspace and response fixtures.
Source
react-console:lib/api/dashboard.ts:useDashboardSummary
05 Demonstration arithmetic exposes its empty-total boundaryedgeunitnegativeproposed
Proves
BR-CAP-PFM-CSH-004-08
Preconditions
Dashboard fixtures contain ordinary amounts, falling dues and zero totals.
Steps
Render amount, regional-share and event-fill calculations for those fixtures.
Expected
Ordinary cases follow the current precision and sign treatment; zero divisors expose the unresolved unreadable percentage.
Data
Independent fixture inputs for the variants listed in this case.
Source
react-console:components/console/home/dashboard-panels.tsx:RegionBreakdown, EventsPanel; components/console/home/kpi-cards.tsx:KpiCards
06 An older home link resolves into the chosen workspaceinteractionbrowserproposed
Proves
BR-CAP-PFM-CSH-004-04 BR-CAP-PFM-CSH-012-01
Preconditions
A customer session remembers its sandbox.
Steps
Follow the older home address after opening the bare console root.
Expected
The landing and compatible home link use the established customer workspace rather than HQ.
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-004-start-the-day-from-the-workspace-home.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