ATS-PFM-CSH-017 Understand the workspace’s application availability — acceptance
Markdown Planning / Platform / Console Shell and Navigation / Application access in the console / Capability Test Specification Test Scenarios 12 scenarios proving CAP-PFM-CSH-017
01 The administrator API separates permitted, forbidden and anonymous callers api negative test
Proves BR-CAP-PFM-CSH-017-14Preconditions Callers cover a permitted administrator, a user without the read key and an anonymous session. Steps Request the workspace application list with each caller. Expected The administrator receives the list; the other callers receive forbidden and unauthenticated responses respectively. Data Licensing fixtures and an unsigned request. Bound to Source services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js #serves an administrator of the customer holding platform.tenant-applications.read 02 Ordering and reasons are understandable unit test
Proves BR-CAP-PFM-CSH-017-02BR-CAP-PFM-CSH-017-03BR-CAP-PFM-CSH-017-04Preconditions Application inputs cover available products and each unavailable state. Steps Sort the inputs and generate labels and explanations. Expected Available entries lead each name-ordered group, reasons are sentences, codes stay hidden and an ending licence does not change availability. Data Availability-state and date variants. Bound to Source react-console:lib/applications/availability.test.ts #lists the available applications first, then by name 04 The administrator overview presents an available application in plain words browser test
Proves BR-CAP-PFM-CSH-017-03Preconditions The development fixture supplies an available application. Steps Open the customer administrator’s Applications overview. Expected The fixture’s application displays Available, the list contains several applications and no enum tokens are displayed. Data The development application fixture. Bound to Source react-console:e2e/dev/hq-licensing.dev.spec.ts #the tenant's own administrator reads Configuration › Applications with the same words 05 Initial loading, failure and empty results remain understandable browser negative proposed
Proves BR-CAP-PFM-CSH-017-08Preconditions The application read is delayed, fails or returns no entries. Steps Open the overview for each response. Expected The body presents progress, retry after failure and the empty-list explanation respectively. Data Controlled initial application responses. Source services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js #refuses a console user who does not hold that key, with 403 06 Incomplete records reveal the permissive availability default unit negative proposed
Proves BR-CAP-PFM-CSH-017-11Preconditions A keyed entry omits availability and has unreadable companion states. Steps Parse that entry and one explicitly marked unavailable. Expected The incomplete entry defaults to available; exactly false remains unavailable. Data Incomplete application records. Source react-console:lib/applications/types.ts :parseTenantApplication 07 Date formatting preserves a licence’s calendar day unit test
Proves BR-CAP-PFM-CSH-017-05Preconditions The formatter is loaded in a time zone behind UTC. Steps Format the supplied licence date. Expected The displayed calendar day agrees with Platform’s date. Data A date whose local midnight conversion could change the day. Bound to Source react-console:lib/applications/availability.test.ts #reads a licence date as the day Platform sent it, in a zone behind UTC 08 Parser fallback preserves only identifiable entries unit negative test
Proves BR-CAP-PFM-CSH-017-09Preconditions Inputs include missing keys and unrecognized licence and operational states. Steps Parse the collection. Expected Missing-key entries are removed; unknown states become unlicensed and not set up. Data Parser boundary inputs. Bound to Source react-console:lib/applications/availability.test.ts #takes the records it understands and leaves out the ones it does not 09 The overview menu entry requires its view authority unit negative proposed
Proves BR-CAP-PFM-CSH-017-10Preconditions Navigation inputs include and omit the application-view key. Steps Build Configuration application links. Expected The overview appears first when permitted and is omitted otherwise. Data Permission inputs for the overview link. Source react-console:components/console/nav-config.ts :configurationArea 10 Disabled workspace reads retain the explicit reach boundary api negative proposed
Proves BR-CAP-PFM-CSH-017-12Preconditions The requested workspace is disabled; callers cover permitted and unrelated customer scopes. Steps Read the workspace application list with both callers. Expected The permitted caller receives the list and the unrelated caller receives not found. Data A disabled workspace and two scoped administrator fixtures. Source services-platform:modules/tenants/aws/api/tenant-applications.routes.ts :tenantApplicationsRoutes 11 The customer answer withholds staff and commercial detail api test
Proves BR-CAP-PFM-CSH-017-13Preconditions The API fixtures include a staff grant, withholding and a suspension with a staff reason. Steps Read the application answer as a customer administrator for each fixture. Expected Application facts remain available while overrides, staff identities and staff reasons are absent; withholding is described as unlicensed. Data Licensing grant, withholding and suspension fixtures. Bound to Source services-platform:modules/licensing/tests/e2e/licensing.e2e.spec.js ← Previous Capability Test Specification ATS-PFM-CSH-016 · Refresh application choices when access changes — acceptance Next Capability Test Specification → ATS-PFM-CSH-018 · Follow a record reference to the right page — acceptance