Enter the workspace named by a link — acceptance

Coverage

The table separates scenarios with test bindings from proposed proof. A binding records a static examination of the test; it does not record a passing product test run.

Rule	Acceptance scenario
`BR-CAP-PFM-CSH-010-01`	`ATS-PFM-CSH-010-01` (proposed)
`BR-CAP-PFM-CSH-010-02`	`ATS-PFM-CSH-010-02` (bound)
`BR-CAP-PFM-CSH-010-03`	`ATS-PFM-CSH-010-03` (proposed)
`BR-CAP-PFM-CSH-010-04`	`ATS-PFM-CSH-010-03` (proposed)
`BR-CAP-PFM-CSH-010-05`	`ATS-PFM-CSH-010-04` (proposed)
`BR-CAP-PFM-CSH-010-08`	no scenario: `FND-PFM-CSH-021`
`BR-CAP-PFM-CSH-010-09`	`ATS-PFM-CSH-010-05` (proposed)
`BR-CAP-PFM-CSH-010-10`	no scenario: `FND-PFM-CSH-021`

Test Scenarios

5 scenarios proving CAP-PFM-CSH-010; 1 bound to an existing test.

01 Workspace entry waits for the requested contextbrowserproposed

Proves: BR-CAP-PFM-CSH-010-01
Preconditions: The person can reach two workspaces.
Steps: Open a page in the second workspace while the first context is established.
Expected: Loading precedes the second workspace page; the first workspace page is not rendered as that destination.
Data: Two mock workspaces and a delayed answer.
Source: react-console:components/console/tenant-id-gate.tsx:TenantIdGate

02 Unknown workspace identity produces not foundbrowsernegativetest

Proves: BR-CAP-PFM-CSH-010-02 AS-JNY-PFM-CSH-003-03
Preconditions: The requested workspace identity is absent.
Steps: Open a destination in that workspace.
Expected: The workspace gate presents not found.
Data: Unknown identities in mock and development contexts.
Bound to: react-console:e2e/mock/url-architecture.mock.spec.ts#an id no tenant has shows not found
react-console:e2e/dev/url-architecture.dev.spec.ts#an id no tenant has shows not found
Source: react-console:e2e/mock/url-architecture.mock.spec.ts#an id no tenant has shows not found

03 Refused entry chooses a valid return contextunitnegativeproposed

Proves: BR-CAP-PFM-CSH-010-03 BR-CAP-PFM-CSH-010-04 AS-JNY-PFM-CSH-004-02
Preconditions: Entry is refused with an established workspace, another reachable workspace or no reachable workspace.
Steps: Evaluate the refusal and return destination.
Expected: The refusal returns to the established workspace where possible, then a reachable alternative, otherwise offers no invalid workspace return.
Data: Contexts covering the return choices.
Source: react-console:components/console/tenant-id-gate.tsx:TenantIdGate, deniedReturnTenant

04 Out-of-service entry explains availabilityunitnegativeproposed

Proves: BR-CAP-PFM-CSH-010-05
Preconditions: A disabled workspace is requested by customer staff and Rhythm staff.
Steps: Render the gate for each session.
Expected: The explanation is unavailability; staff can return to HQ and customer staff can use a reachable alternative.
Data: Refused-entry contexts for both actor types.
Source: react-console:components/console/tenant-id-gate.tsx:TenantIdGate

05 Fresh direct entry requests the named workspace firstbrowserproposed

Proves: BR-CAP-PFM-CSH-010-09
Preconditions: The browser has a signed-in session.
Steps: Load a workspace destination and reload it.
Expected: The initial access request names the workspace and the working page waits for that answer.
Data: A development account and observed request log.
Source: react-console:lib/security-context/provider.tsx:openTenantId

Planning

Enter the workspace named by a link — acceptance ​

Coverage ​

Test Scenarios

Enter the workspace named by a link — acceptance

Coverage