Refresh application choices when access changes — 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-016-01`	`ATS-PFM-CSH-016-01` (bound), `ATS-PFM-CSH-016-02` (bound)
`BR-CAP-PFM-CSH-016-02`	`ATS-PFM-CSH-016-02` (bound)
`BR-CAP-PFM-CSH-016-03`	`ATS-PFM-CSH-016-03` (proposed)
`BR-CAP-PFM-CSH-016-04`	no scenario: `FND-PFM-CSH-021`
`BR-CAP-PFM-CSH-016-05`	no scenario: `FND-PFM-CSH-021`
`BR-CAP-PFM-CSH-016-06`	`ATS-PFM-CSH-016-04` (proposed)

Test Scenarios

4 scenarios proving CAP-PFM-CSH-016; 2 bound to an existing test.

01 An application refusal updates offered workbrowsertest

Proves: BR-CAP-PFM-CSH-016-01
Preconditions: CRM and Membership are initially offered, then mock CRM requests are refused.
Steps: Open Tasks to trigger the refusal path.
Expected: The refreshed menu removes CRM and retains Membership.
Data: Mock application refusal responses.
Bound to: react-console:e2e/mock/application-access.mock.spec.ts#brings the launcher up to date instead of leaving it offering what is gone
Source: react-console:e2e/mock/application-access.mock.spec.ts#brings the launcher up to date instead of leaving it offering what is gone

02 Only application-specific refusal codes notify listenersunitnegativetest

Proves: BR-CAP-PFM-CSH-016-01 BR-CAP-PFM-CSH-016-02
Preconditions: Responses cover both application codes and unrelated refusal codes.
Steps: Report each refusal to registered listeners.
Expected: Application refusals notify each listener once; other refusals produce no notification.
Data: Refusal-code variants and registered listeners.
Bound to: react-console:lib/security-context/application-refusal.test.ts#reads the two application codes off a 403
react-console:lib/security-context/application-refusal.test.ts#leaves every other refusal alone
react-console:lib/security-context/application-refusal.test.ts#calls every listener once, with the code
Source: react-console:lib/security-context/application-refusal.test.ts#reads the two application codes off a 403

03 Returning to an old tab refreshes application answersunitproposed

Proves: BR-CAP-PFM-CSH-016-03
Preconditions: The last application read is six minutes old.
Steps: Bring the tab to the foreground.
Expected: One application refresh is requested.
Data: A controlled clock and request observer.
Source: react-console:lib/security-context/provider.tsx:SecurityContextProvider

04 A prior-workspace refresh cannot replace the new answerunitnegativeproposed

Proves: BR-CAP-PFM-CSH-016-06
Preconditions: An application refresh is pending in the old workspace.
Steps: Enter another workspace, then resolve the earlier request.
Expected: The new workspace application list remains unchanged by the late answer.
Data: Delayed refresh and workspace-entry responses.
Source: react-console:lib/security-context/provider.tsx:refreshApplications

Planning

Refresh application choices when access changes — acceptance ​

Coverage ​

Test Scenarios

Refresh application choices when access changes — acceptance

Coverage