ATS-PFM-TNL-011Control the initial import and subsequent opening: Acceptance Test Set
MarkdownTest Scenarios
6 scenarios proving CAP-PFM-TNL-011; 6 bound to an existing test.
01 Loading requires import authorityapinegativetest
- Proves
BR-CAP-PFM-TNL-011-01 - Preconditions
- An implementation workspace is targeted by activation-only, customer and anonymous identities.
- Steps
- Attempt to open loading with each identity.
- Expected
- All requests are refused.
- Data
- Use the workspace, caller and collaborator fixtures declared by the bound tests.
- Bound to
- Source
- services-platform:modules/tenants/tests/e2e/hq-tenant-loading.e2e.spec.js#refuses the staff member who may only activate a tenant, the two keys being separate
02 Live workspaces cannot enter initial loadingapinegativetest
- Proves
BR-CAP-PFM-TNL-011-02 - Preconditions
- The workspace has live business status.
- Steps
- Request loading.
- Expected
- The status requirement is reported and the workspace remains unchanged.
- Data
- Use the workspace, caller and collaborator fixtures declared by the bound tests.
- Bound to
- Source
- services-platform:modules/tenants/tests/e2e/hq-tenant-loading.e2e.spec.js#refuses a live tenant, an initial import going only into an implementation tenant
03 Load opening retains its original attributionapitest
- Proves
BR-CAP-PFM-TNL-011-03 - Preconditions
- An implementation workspace has not entered loading.
- Steps
- Open loading with a reason, then repeat the action.
- Expected
- Operator, time and explanation are recorded once and preserved on repetition.
- Data
- Use the workspace, caller and collaborator fixtures declared by the bound tests.
- Bound to
- Source
- services-platform:modules/tenants/tests/e2e/hq-tenant-loading.e2e.spec.js#is served to a staff member holding hq.data-runs.manage, answering the loading state
04 Import permission cannot activateapinegativetest
- Proves
BR-CAP-PFM-TNL-011-04 - Preconditions
- A workspace is loading and callers exercise import-only, customer, anonymous and activation authority.
- Steps
- Attempt activation for each.
- Expected
- Only the caller with activation authority succeeds.
- Data
- Use the workspace, caller and collaborator fixtures declared by the bound tests.
- Bound to
- Source
- services-platform:modules/tenants/tests/e2e/hq-tenant-loading.e2e.spec.js#refuses the staff member who ran the import, activation being the other key
05 Activation leaves business mode unchangedapitest
- Proves
BR-CAP-PFM-TNL-011-05 - Preconditions
- The workspace is loading in implementation mode.
- Steps
- Activate the completed load.
- Expected
- Lifecycle becomes active while implementation status and load history remain.
- Data
- Use the workspace, caller and collaborator fixtures declared by the bound tests.
- Bound to
- Source
- services-platform:modules/tenants/tests/e2e/hq-tenant-loading.e2e.spec.js#is served to a staff member holding hq.tenants.activate, returning the tenant to active
06 Import journey separates activation from go-liveapitest
- Proves
AS-JNY-PFM-TNL-003-02 - Preconditions
- The import journey reaches its approved load fixture.
- Steps
- Activate and inspect its status.
- Expected
- Customer availability returns without an automatic change to live business mode.
- Data
- Use the workspace, caller and collaborator fixtures declared by the bound tests.
- Bound to
- Source
- services-platform:modules/tenants/tests/e2e/hq-tenant-loading.e2e.spec.js#leaves the status where it was, going live being the separate decision