Rhythm 2.0 Specifications

Appearance

ATS-PFM-TNL-010Supply application data for workspace exports: Acceptance Test Set

Markdown

ATS-PFM-TNL-010

Supply application data for workspace exports: Acceptance Test Set

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-PFM-TNL-010

KindAcceptance test setProduct areaPlatformModuleWorkspace Lifecycle Across ApplicationsRevision2

Read atservices-platform ad3f6a65services-crm a8d1364fservices-commerce c8b66a98services-membership 5994c270services-submissions 64236c19services-websites 5fc6823c

Test Scenarios

4 scenarios proving CAP-PFM-TNL-010; 4 bound to an existing test.

01 Dataset continuation spans multiple partsapitest
Proves
BR-CAP-PFM-TNL-010-01
Preconditions
The requested workspace has more records than one batch.
Steps
Page the export until completion.
Expected
Each batch supplies part information and continuation until no records remain.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
services-crm:modules/tenant-lifecycle/tests/integration/services/export/tenant-export.integration.spec.js#pages a dataset of more records than a batch holds, the cursor carrying it on
Source
services-crm:modules/tenant-lifecycle/tests/integration/services/export/tenant-export.integration.spec.js#pages a dataset of more records than a batch holds, the cursor carrying it on
02 Export classifications cover declarationsunittest
Proves
BR-CAP-PFM-TNL-010-02
Preconditions
The exporting applications expose datasets and resources.
Steps
Check the resource-to-dataset classifications.
Expected
Every declared resource has a classification and exported resources have one dataset home.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
services-crm:modules/tenant-lifecycle/tests/integration/services/export/tenant-export.integration.spec.js#exports every row of the tenant’s exported tables exactly once, in its record or inline on its parent
services-crm:modules/tenant-lifecycle/tests/integration/services/export/tenant-export.integration.spec.js#withholds every declared table it does not export, each with its class and reason
services-websites:modules/tenant-lifecycle/tests/unit/participants/export-coverage.spec.js#classifies every resource, gathers every exported one in exactly one dataset, and has no dataset problem
services-membership:modules/tenant-lifecycle/tests/unit/export-coverage.spec.ts#classifies every resource, gathers each exported one in one dataset of its own participant and covers every object
Source
services-crm:modules/tenant-lifecycle/tests/integration/services/export/tenant-export.integration.spec.js#exports every row of the tenant’s exported tables exactly once, in its record or inline on its parent
03 Export values remain isolatedapitest
Proves
BR-CAP-PFM-TNL-010-03
Preconditions
Two workspaces contain distinguishable data.
Steps
Export one workspace.
Expected
Output identifies that workspace and includes none of its neighbor’s values.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
Source
services-crm:modules/tenant-lifecycle/tests/integration/services/export/tenant-export.integration.spec.js#stamps every record with the exported tenant
04 CRM rejects foreign export destinationsapinegativetest
Proves
BR-CAP-PFM-TNL-010-04
Preconditions
Requests name an undeclared dataset or foreign staging prefix.
Steps
Dispatch each CRM export request.
Expected
Invalid destinations refuse before reading and unsupported datasets are identified.
Data
Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to
services-crm:modules/tenant-lifecycle/tests/integration/services/export/tenant-export.integration.spec.js#answers blocked for a dataset the participant does not declare, naming it
services-crm:modules/tenant-lifecycle/tests/integration/services/export/tenant-export.integration.spec.js#answers blocked for a staging bucket other than the one this deploy may write to
services-crm:modules/tenant-lifecycle/tests/integration/services/export/tenant-export.integration.spec.js#refuses a staging prefix outside this service’s own as an invalid request, before anything is read
Source
services-crm:modules/tenant-lifecycle/tests/integration/services/export/tenant-export.integration.spec.js#answers blocked for a dataset the participant does not declare, naming 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