Skip to content

ATS-PFM-CSH-010Enter the workspace named by a link: Capability Test Specification

Markdown

ATS-PFM-CSH-010

Enter the workspace named by a link: Capability Test Specification

Markdown
  • DocumentProposed

KindAcceptance test setProduct areaPlatformModuleConsole Shell and NavigationRevision3

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

Coverage

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

Test Scenarios

9 scenarios proving CAP-PFM-CSH-010; 4 bound to an existing test.

01 The new page waits for its requested workspaceinvariantbrowserproposed
Proves
BR-CAP-PFM-CSH-010-01
Preconditions
A person can enter two workspaces and holds the first context.
Steps
Open work in the second while delaying its context response.
Expected
The destination waits; the first workspace body is not rendered as the second workspace’s content.
Data
An isolated browser context with the stated identity, workspace and response fixtures.
Source
react-console:components/console/tenant-id-gate.tsx:TenantIdGate
02 An absent workspace identity yields not foundvalidationbrowsernegativetest
Proves
BR-CAP-PFM-CSH-010-02 AS-JNY-PFM-CSH-003-03
Preconditions
The requested workspace identity is not registered.
Steps
Open that identity’s destination in the mock and development fixtures.
Expected
The workspace gate presents its not-found outcome.
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#an id no tenant has shows not found
03 Refusal selects only a reachable return destinationpermissionunitnegativetest
Proves
BR-CAP-PFM-CSH-010-03 BR-CAP-PFM-CSH-010-04 AS-JNY-PFM-CSH-004-02
Preconditions
Fixtures cover a held workspace, another reachable workspace and no valid alternative.
Steps
Evaluate customer denial and its return-workspace choices.
Expected
The held workspace wins when usable, otherwise a reachable alternative wins, and no invalid return is offered.
Data
Independent fixture inputs for the variants listed in this case.
Bound to
Source
react-console:components/console/__tests__/tenant-id-gate.test.tsx#leaves anyone else on the access-denied page
04 Disabled workspace entry remains an availability refusalvalidationunitnegativetest
Proves
BR-CAP-PFM-CSH-010-05
Preconditions
Staff and customer fixtures request a disabled workspace.
Steps
Evaluate the unavailable panel and each return choice.
Expected
The explanation names unavailability; staff can return to HQ and customers can return to another reachable workspace.
Data
Independent fixture inputs for the variants listed in this case.
Bound to
Source
react-console:components/console/__tests__/tenant-id-gate.test.tsx#says the workspace is unavailable, never no access, with the way back for staff
05 Direct startup reuses its named-workspace answerrulebrowserproposed
Proves
BR-CAP-PFM-CSH-010-09
Preconditions
The browser starts signed in at a direct workspace destination.
Steps
Capture the initial context request, gate entry and reload.
Expected
The request names the destination workspace; content waits and the gate reuses the matching boot answer rather than requesting it again.
Data
An isolated browser context with the stated identity, workspace and response fixtures.
Source
react-console:lib/security-context/provider.tsx:openTenantId
06 A strict read refuses the wrong workspace answerinvariantunitnegativetest
Proves
BR-CAP-PFM-CSH-010-01 INV-DOM-PFM-CSH-003-02
Preconditions
The requested workspace differs from the returned context.
Steps
Return a successful context response naming the default workspace instead.
Expected
The strict reader rejects the answer and emits a warning rather than confirming entry.
Data
Independent in-memory fixtures for each listed input.
Bound to
Source
react-console:lib/security-context/tenant-id.test.ts#refuses a 200 about another tenant than the one asked for, warning in the console
07 Unexpected entry failure remains a failurefailurebrowsernegativeproposed
Proves
BR-CAP-PFM-CSH-010-08
Preconditions
The requested workspace read raises an unclassified error.
Steps
Open its destination and await the failed answer.
Expected
The gate displays the failure message without granting entry or substituting another working page.
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-010-enter-the-workspace-an-address-names-or-learn-why-not.md
08 Encoded workspace identity is compared without casevalidationbrowserproposed
Proves
BR-CAP-PFM-CSH-010-10
Preconditions
The URL encodes characters in a mixed-case reachable workspace identity.
Steps
Open the address against a lowercased matching context.
Expected
Entry decodes and lowercases the address identity before comparing it; no false mismatch remains.
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-010-enter-the-workspace-an-address-names-or-learn-why-not.md
09 Switch entry withholds the old record from the new workspaceinteractionbrowserproposed
Proves
BR-CAP-PFM-CSH-010-01 BR-CAP-PFM-CSH-011-07
Preconditions
A contact is open and the sandbox context read is delayed.
Steps
Select the sandbox, then complete entry.
Expected
The pending destination shows no old contact body; successful entry clears SWR answers and mounts fresh workspace stores before the new list renders.
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-010-enter-the-workspace-an-address-names-or-learn-why-not.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.