The structured coverage rows link required rules to their scenarios. A covered category has a defined check; executable coverage and successful execution require separate evidence. The category map keeps incomplete lifecycle matrices and other missing checks visible as findings.
Reset removes loaded mappings before reconciliation and reload. Failed loading remains available for reset and a fresh run. Reset keeps input available while deletion removes it. The interaction scenarios use the related capabilities' rule references and identify the shared fixture and observable outcome.
Coverage
Rulecovered
Transitiongap: FND-PFM-DJE-077
Validationcovered
Permissioncovered
Edgegap: FND-PFM-DJE-077
Failuregap: FND-PFM-DJE-077
Boundarycovered
Concurrencygap: FND-PFM-DJE-077
Invariantcovered
Interactioncovered
Test Scenarios
10 scenarios proving CAP-PFM-DJE-017; 2 bound to an existing test.
01Reset eligibility and confirmation are requiredvalidationapinegativeproposed
[
{
"do": "Request resets and use incorrect confirmation for the loading workspace.",
"expect": "The proposed refusal checks expect no removal from ineligible or incorrectly confirmed requests.",
"provenance": "proposed",
"source": "react-console:acceptance/crm/playwright/journeys/data-operations/CRM-ACC-0674.spec.ts#CRM-ACC-0674"
}
]
Expected
The proposed refusal checks expect no removal from ineligible or incorrectly confirmed requests.
[
{
"do": "Reset its participants.",
"expect": "The cited fixtures report participant completion and removal of loaded CRM records, types and keys.",
"provenance": "test",
"source": "services-crm:modules/data-jobs/tests/integration/services/jobs/initial-import-guarantees.integration.spec.js#answers done from every participant of the reset"
}
]
Expected
The cited fixtures report participant completion and removal of loaded CRM records, types and keys.
[
{
"do": "Request reset.",
"expect": "The service is named in a refusal before any participant is emptied.",
"provenance": "proposed",
"source": "services-platform:docs/data-jobs/tenant-reset.md#3.1 Declaring support"
}
]
Expected
The service is named in a refusal before any participant is emptied.
[
{
"do": "Reset and reload one workspace.",
"expect": "The other retains its checksum and the reloaded records and numbers match the prior load.",
"provenance": "test",
"source": "services-crm:modules/data-jobs/tests/integration/services/jobs/initial-import-guarantees.integration.spec.js#leaves every row of the other loading tenant as it was, by a checksum of each table"
}
]
Expected
The other retains its checksum and the reloaded records and numbers match the prior load.
Use a staff caller with loading access but without activation access.
Steps
[
{
"do": "Request activation.",
"expect": "The proposed API proof expects refusal.",
"provenance": "proposed",
"source": "services-platform:docs/data-jobs/data-runs.md#7. The summary and the readiness verdict"
}
]
[
{
"do": "Attempt activation, resolve the blockers and attempt again.",
"expect": "The proposed gate refuses the first request with blockers and permits release after resolution.",
"provenance": "proposed",
"source": "services-platform:docs/milestones/plans/PLAT-M22-plan.md#A3"
}
]
Expected
The proposed gate refuses the first request with blockers and permits release after resolution.
[
{
"do": "Call an ordinary route and an allowed data-job route.",
"expect": "The ordinary request is unavailable and the allowed job request is served.",
"provenance": "proposed",
"source": "react-console:acceptance/crm/playwright/journeys/data-operations/CRM-ACC-0673.spec.ts#CRM-ACC-0673"
}
]
Expected
The ordinary request is unavailable and the allowed job request is served.
Load the same package in two isolated loading workspaces.
Steps
[
{
"do": "Reset one, reconcile its keys, reload it, and compare both workspaces with their prior projections.",
"expect": "Reset keys become missing until reload; the other workspace remains unchanged and the reset fixture reproduces its records and numbers.",
"provenance": "proposed",
"source": "services-crm:modules/data-jobs/services/jobs/records-by-source-key.ts:readRecordsBySourceKey; services-platform:modules/data-jobs/services/jobs/records-by-source-key.ts:readCustomFieldsBySourceKey; services-crm:modules/data-jobs/tests/integration/services/jobs/records-by-source-key.integration.spec.js#looks a key up under its own object type only: a contact key is not an organization; services-crm:modules/data-jobs/tests/integration/services/jobs/initial-import-guarantees.integration.spec.js#removes everything the load wrote: no contact, organization, imported type or crosswalk row is left; services-crm:modules/data-jobs/tests/integration/services/jobs/initial-import-guarantees.integration.spec.js#reloads the same records as the load before the reset, numbers included"
}
]
Expected
Reset keys become missing until reload; the other workspace remains unchanged and the reset fixture reproduces its records and numbers.
Data
Load the same package in two isolated loading workspaces.
Start a package with a dataset that fails after earlier work committed.
Steps
[
{
"do": "Inspect the failed run, reset the loading workspace, register corrected input and reload.",
"expect": "Earlier commits remain until reset; a new registration drives the corrected load without reopening the failed run.",
"provenance": "proposed",
"source": "services-platform:modules/data-jobs/tests/integration/services/runs/run-driver.integration.spec.js#cancels the jobs a cancelled run had already submitted, in their own services; services-platform:modules/data-jobs/tests/unit/run-summary.spec.ts#is not ready when a dataset’s counts do not add up to what the producer claimed; services-crm:modules/data-jobs/tests/integration/services/jobs/initial-import-guarantees.integration.spec.js#removes everything the load wrote: no contact, organization, imported type or crosswalk row is left; services-crm:modules/data-jobs/tests/integration/services/jobs/initial-import-guarantees.integration.spec.js#reloads the same records as the load before the reset, numbers included; services-platform:docs/data-jobs/tenant-reset.md#1. When a tenant may be reset"
}
]
Expected
Earlier commits remain until reset; a new registration drives the corrected load without reopening the failed run.
Data
Start a package with a dataset that fails after earlier work committed.
Prepare completed uploads and loaded records in a loading workspace.
Steps
[
{
"do": "Reset the workspace, inspect retained uploads, reload from them, then invoke workspace deletion on a separate disposable fixture.",
"expect": "Reset retains input for another load; deletion removes its upload records and stored versions.",
"provenance": "proposed",
"source": "services-platform:docs/data-jobs/uploads.md#Deletion; services-crm:modules/data-jobs/tests/integration/services/jobs/initial-import-guarantees.integration.spec.js#removes everything the load wrote: no contact, organization, imported type or crosswalk row is left; services-crm:modules/data-jobs/tests/integration/services/jobs/initial-import-guarantees.integration.spec.js#reloads the same records as the load before the reset, numbers included"
}
]
Expected
Reset retains input for another load; deletion removes its upload records and stored versions.
Data
Prepare completed uploads and loaded records in a loading workspace.