Rhythm 2.0 Specifications

Appearance

ATS-PFM-TNL-008Apply defaults without undoing customer choices: Acceptance Test Set

Markdown

ATS-PFM-TNL-008

Apply defaults without undoing customer choices: Acceptance Test Set

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-TNL-008

KindAcceptance test setProduct areaPlatformModuleWorkspace Lifecycle Across ApplicationsRevision2

Read atservices-platform ad3f6a65services-crm a8d1364fservices-commerce c8b66a98services-committees 36129c24

Test Scenarios

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

01 First seed application retains its runapitest
Proves
BR-CAP-PFM-TNL-008-01
Preconditions
A workspace has no seed entries for the set.
Steps
Apply the set.
Expected
Each applied seed has one ledger row referring to the applying run.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
Source
services-platform:modules/tenants/tests/integration/services/persistence/tenant-seed-applications.integration.spec.js#applies every seed of the set and records each against the run that wrote it
02 Customer customization survives seed replayapitest
Proves
BR-CAP-PFM-TNL-008-02
Preconditions
A seeded workspace has one renamed and one deleted default.
Steps
Repeat provisioning.
Expected
The edited record stays edited and the removed record stays absent.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
services-crm:modules/tenant-lifecycle/tests/integration/services/participants/provisioning.integration.spec.js#leaves a type the customer renamed after it was seeded exactly as they left it
Source
services-crm:modules/tenant-lifecycle/tests/integration/services/participants/provisioning.integration.spec.js#does not recreate a default the customer deleted
03 Natural-key matches are adoptedapitest
Proves
BR-CAP-PFM-TNL-008-03
Preconditions
A customer-created record matches a seed’s key.
Steps
Apply the seed set.
Expected
The original record is preserved and its adoption is ledgered.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
services-crm:modules/tenant-lifecycle/tests/integration/services/participants/provisioning.integration.spec.js#adopts a role the customer made first with a seed’s id, rather than duplicating it
services-crm:modules/tenant-lifecycle/tests/integration/services/participants/provisioning.integration.spec.js#records an adopted role in the ledger too, so it is never written over later
services-crm:modules/tenant-lifecycle/tests/integration/services/participants/activities-provisioning.integration.spec.js#adopts a type the customer made first under a seed’s id, rather than overwriting it
services-committees:modules/tenant-lifecycle/tests/integration/services/starter-types.integration.spec.ts#adopts the position the customer made under a starter’s id instead of overwriting it
Source
services-crm:modules/tenant-lifecycle/tests/integration/services/participants/provisioning.integration.spec.js#adopts a role the customer made first with a seed’s id, rather than duplicating it
04 Readiness identifies missing seed entriesapitest
Proves
BR-CAP-PFM-TNL-008-05
Preconditions
Fixtures represent a workspace before and after provisioning.
Steps
Evaluate participant readiness in both fixtures.
Expected
Missing entries are named before provisioning and none are missing afterward.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
services-commerce:modules/tenant-lifecycle/tests/integration/services/participants/orders-participant.integration.spec.js#answers verifyProvisioned not ready for a fresh tenant, naming the two built-in audiences
Source
services-crm:modules/tenant-lifecycle/tests/integration/services/participants/provisioning.integration.spec.js#answers not ready, naming every seed, before it has provisioned
05 Seed ledgers remain workspace-scopedapitest
Proves
BR-CAP-PFM-TNL-008-06
Preconditions
Two distinct workspaces are available.
Steps
Apply seeds in one and inspect from the other.
Expected
The second workspace cannot see or change the first ledger.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
Source
services-platform:modules/tenants/tests/integration/services/persistence/tenant-seed-applications.integration.spec.js#keeps one tenant’s ledger out of another tenant’s reach
06 Baseline replay adds no duplicateapitest
Proves
AS-JNY-PFM-TNL-005-02
Preconditions
The baseline journey has already applied its seed sets.
Steps
Repeat the reconciliation fixture.
Expected
No additional default or seed entry is created.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
Source
services-crm:modules/tenant-lifecycle/tests/integration/services/participants/provisioning.integration.spec.js#skips every seed on a second provisioning
07 Baseline respects renamed defaultsapitest
Proves
AS-JNY-PFM-TNL-005-03
Preconditions
The baseline journey includes customized seed records.
Steps
Reconcile after rename or deletion.
Expected
The customer’s changes remain as recorded.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
services-crm:modules/tenant-lifecycle/tests/integration/services/participants/provisioning.integration.spec.js#leaves a type the customer renamed after it was seeded exactly as they left it
Source
services-crm:modules/tenant-lifecycle/tests/integration/services/participants/provisioning.integration.spec.js#leaves a type the customer renamed after it was seeded exactly as they left it

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