Rhythm 2.0 Specifications

Appearance

ATS-PFM-TNL-002Open a workspace after its applications are ready: Acceptance Test Set

Markdown

ATS-PFM-TNL-002

Open a workspace after its applications are ready: Acceptance Test Set

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-TNL-002

KindAcceptance test setProduct areaPlatformModuleWorkspace Lifecycle Across ApplicationsRevision2

Read atservices-platform ad3f6a65

Test Scenarios

7 scenarios proving CAP-PFM-TNL-002; 7 bound to an existing test.

01 Dependencies determine construction orderunittest
Proves
BR-CAP-PFM-TNL-002-01
Preconditions
Participant declarations include their prerequisites.
Steps
Derive the plan and step catalog.
Expected
The workspace comes first and participants appear once before readiness and activation.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
services-platform:modules/tenants/tests/unit/services/provisioning/provision-tenant-workflow.spec.js#has one step per planned participant, then the readiness check and the activation
services-platform:modules/tenants/tests/integration/services/provisioning/provision-tenant.integration.spec.js#provisions all seven of CRM’s participants, the tasks, activities and duplicates participants after the entities they depend on
Source
services-platform:modules/tenants/tests/unit/services/provisioning/provision-tenant-workflow.spec.js#runs the tenant row before anything that depends on it
02 Live declaration drift stops executionapinegativetest
Proves
BR-CAP-PFM-TNL-002-02
Preconditions
Live descriptions differ from the static participant order.
Steps
Start the lifecycle plan.
Expected
The refusal reports planned and current participants before their work runs.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
services-platform:modules/tenants/tests/unit/services/provisioning/provision-tenant-workflow.spec.js#refuses a run whose participants are not the ones it was planned for, naming both plans
services-platform:modules/tenants/tests/unit/services/lifecycle/remote-participants.spec.js#plans the live manifests, so normalised, in exactly the order the static copies plan (what the publish step compares)
services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge.integration.spec.js#refuses the purge as planned for other participants rather than skipping one
Source
services-platform:modules/tenants/tests/unit/services/provisioning/provision-tenant-workflow.spec.js#refuses a run whose participants are not the ones it was planned for, naming both plans
03 Enablement controls remote constructionapitest
Proves
BR-CAP-PFM-TNL-002-03
Preconditions
Fixtures include enabled remote participants and a disabled application.
Steps
Provision under each registry configuration.
Expected
Enabled participants are invoked and the disabled application receives no description or work call.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
services-platform:modules/tenants/tests/integration/services/provisioning/provision-tenant.integration.spec.js#asks the other macroservice to provision each of its participants, for the tenant being provisioned
services-platform:modules/tenants/tests/integration/services/provisioning/provision-tenant.integration.spec.js#neither describes nor asks Accounting while a registry that switches Accounting’s participants off is in force
Source
services-platform:modules/tenants/tests/integration/services/provisioning/provision-tenant.integration.spec.js#asks the other macroservice to provision each of its participants, for the tenant being provisioned
04 Readiness retains a missing-resource failureapinegativetest
Proves
BR-CAP-PFM-TNL-002-04
Preconditions
A participant cannot account for a required resource.
Steps
Run construction through readiness.
Expected
The missing resource is reported and the workspace stays closed.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
services-platform:modules/tenants/tests/integration/services/provisioning/provision-tenant.integration.spec.js#asks every participant to confirm what it made before the tenant is opened
Source
services-platform:modules/tenants/tests/integration/services/provisioning/provision-tenant.integration.spec.js#asks every participant to confirm what it made before the tenant is opened
05 Activation retains its first openingapitest
Proves
BR-CAP-PFM-TNL-002-05
Preconditions
All construction participants report readiness.
Steps
Activate the workspace and repeat activation.
Expected
Active lifecycle uses the requested mode and the recorded activation time remains stable.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js#shows one step per participant, then the readiness check and the activation
Source
services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js#leaves the tenant usable once the job has run
06 Retry omits completed constructionapitest
Proves
BR-CAP-PFM-TNL-002-06
Preconditions
An earlier attempt stopped after partial completion.
Steps
Run a replacement attempt.
Expected
Outstanding resources are supplied without repeating completed participant work.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
services-platform:modules/tenants/tests/integration/services/provisioning/provision-tenant.integration.spec.js#does the missing work and not the finished work when it is provisioned again
services-platform:modules/tenants/tests/integration/services/provisioning/provision-tenant.integration.spec.js#does not repeat work the other macroservice completed before it lost the answer
Source
services-platform:modules/tenants/tests/integration/services/provisioning/provision-tenant.integration.spec.js#does the missing work and not the finished work when it is provisioned again
07 Construction progress satisfies its journey assertionapitest
Proves
AS-JNY-PFM-TNL-001-02
Preconditions
The provisioning journey’s fixture has a successful build.
Steps
Inspect the resulting build snapshot.
Expected
Participant, readiness and activation steps are present and completed.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js#shows one step per participant, then the readiness check and the activation
Source
services-platform:modules/tenants/tests/e2e/tenant-provisioning.e2e.spec.js#shows one step per participant, then the readiness check and the activation

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.

Rhythm Software