Retain deletion evidence and prevent identifier reuse: Acceptance Test Set

Coverage

Test Scenarios

6 scenarios proving CAP-PFM-TNL-018; 6 bound to an existing test.

01 Completion retains numeric evidenceapitest

Proves: BR-CAP-PFM-TNL-018-01
Preconditions: The purge fixture has completed.
Steps: Read its deletion request.
Expected: Removal totals and zero-result verification remain available.
Data: Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to: services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge.integration.spec.js#records on the request what was removed, and the counts it verified
Source: services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge.integration.spec.js#records on the request what was removed, and the counts it verified

02 Request identity survives workspace removalapitest

Proves: BR-CAP-PFM-TNL-018-02
Preconditions: Deletion removed the workspace record.
Steps: Read the retained request.
Expected: Its copied identity, actors and dates remain readable.
Data: Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to: services-platform:modules/tenants/tests/integration/services/deletion/request-deletion.integration.spec.js#copies the tenant name and customer, so the record still reads after the tenant is gone
services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge.integration.spec.js#keeps the deletion’s own job rows, which are the record of what was done
Source: services-platform:modules/tenants/tests/integration/services/deletion/request-deletion.integration.spec.js#copies the tenant name and customer, so the record still reads after the tenant is gone

03 External ledger retains completed deletionapitest

Proves: BR-CAP-PFM-TNL-018-03
Preconditions: The purge fixture completed its outside-database work.
Steps: Read the workspace’s ledger entry.
Expected: The completed dates and count evidence appear in its retained entry.
Data: Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to: services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge.integration.spec.js#writes the permanent deletion record outside the database, keyed by the tenant
services-platform:modules/tenants/tests/unit/services/deletion/deletion-ledger.spec.js#answers no entry for a tenant the ledger does not hold
Source: services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge.integration.spec.js#writes the permanent deletion record outside the database, keyed by the tenant

04 Retired identity cannot be provisioned againapinegativetest

Proves: BR-CAP-PFM-TNL-018-04
Preconditions: A completed deletion ledger entry exists.
Steps: Request creation under the same identifier.
Expected: The refusal identifies retirement and its deletion request.
Data: Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to: services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-recovery.integration.spec.js#refuses to create a tenant again under the id of one that was deleted
Source: services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-recovery.integration.spec.js#refuses to create a tenant again under the id of one that was deleted

05 Legacy immediate delete changes nothingapinegativetest

Proves: BR-CAP-PFM-TNL-018-08
Preconditions: Fixtures include present and absent workspaces.
Steps: Invoke immediate deletion for both.
Expected: The same refusal directs callers to requests and preserves the present workspace.
Data: Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to: services-platform:modules/tenants/tests/e2e/tenants.e2e.spec.js#answers the gone status the error contract can express
services-platform:modules/tenants/tests/e2e/tenants.e2e.spec.js#points the caller at the deletion request route
services-platform:modules/tenants/tests/e2e/tenants.e2e.spec.js#leaves the tenant exactly as it was, which is the point of refusing
services-platform:modules/tenants/tests/e2e/tenants.e2e.spec.js#answers the same to a tenant that does not exist, because nothing is read before the refusal
Source: services-platform:modules/tenants/tests/e2e/tenants.e2e.spec.js#answers the gone status the error contract can express

06 Deletion journey retains evidence and retirementapitest

Proves: AS-JNY-PFM-TNL-004-04
Preconditions: The deletion journey completed its fixture.
Steps: Read retained counts and attempt identifier reuse.
Expected: Numeric history remains and creation refuses the retired identifier.
Data: Use the workspace, caller and collaborator fixtures declared by the bound tests.
Bound to: services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge.integration.spec.js#records on the request what was removed, and the counts it verified
services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge-recovery.integration.spec.js#refuses to create a tenant again under the id of one that was deleted
Source: services-platform:modules/tenants/tests/integration/services/deletion/tenant-purge.integration.spec.js#records on the request what was removed, and the counts it verified