Each scenario names the guarantee it proves. Category coverage describes specified cases; executable bindings retain their narrower assertion boundaries. Lifecycle coverage remains a gap wherever guards and effects lack independent verification.
Create a valid personal declaration and an HQ declaration with a channel mapping; retain stored preferences for both. Register both declarations, publish one occurrence of each, then inspect rendered content and selected channels.
The interaction case combines the producing, processing and reading outcomes named in its frontmatter. It remains proposed until an executable suite performs that complete sequence.
Coverage
Rulecovered
Transitiongap: FND-PFM-NOT-062
Validationcovered
Permissioncovered
Edgegap: FND-PFM-NOT-062
Failurecovered
Boundarycovered
Concurrencygap: FND-PFM-NOT-062
Invariantcovered
Interactioncovered
Test Scenarios
15 scenarios proving CAP-PFM-NOT-001; 13 bound to an existing test.
01Reject foreign, duplicate and invalid keysvalidationapinegativetest
Prepare a registry with one application's definitions.
Steps
Submit for registration a manifest with a key of another application; next one with a key declared twice; next a key that is not three lowercase words.
Expected
Registration identifies the invalid definition and field, rejects the manifest and leaves the registry unchanged.
Prepare a manifest that passes baseline validation.
Steps
Modify, separately, the category, severity, preference mode, delivery requirement, supersede scope and audience kinds to values outside their lists, and remove every audience kind.
Expected
Each invalid enumeration or empty audience-type list produces a field-specific registration rejection.
Prepare a manifest that passes baseline validation.
Steps
Submit for registration a schema open at its root; one that is not JSON Schema; one with a field named recipient; an example the schema rejects; no examples; eleven examples.
Expected
Each invalid schema or example is rejected with its definition and field identified.
Prepare a manifest that passes baseline validation.
Steps
Submit for registration templates that read an undeclared field; that do not parse; that render a 141-character title; a 307-character text; no English; a supported channel with no template.
Expected
Invalid wording rejects the declaration with a precise location; a valid manifest becomes visible in the HQ catalog.
Prepare a application with a published API registry.
Steps
Submit for registration a destination with an undeclared placeholder; an operation action naming an operation the API lacks; one that is not a console route; a valid one.
Expected
The three invalid declarations fail; a valid operation action retains the permission required by its console route.
Prepare a application with two registered definitions.
Steps
Submit for registration the identical manifest a second time; a manifest that changes one; a manifest that removes one; a manifest that declares it a second time.
Expected
Identical content causes no write; changed content becomes version two under the new release; omission retires without deletion; redeclaration reactivates.
Prepare a organization with one open and one settled request of a definition, and settings of it.
Steps
Submit for registration a manifest that no longer declares the definition.
Expected
The open request becomes cancelled and settled; the settled request and stored workspace settings stay unchanged. Existing notices and queued deliveries remain in place.
Create a valid personal declaration and an HQ declaration with a channel mapping; retain stored preferences for both.
Steps
Register both declarations, publish one occurrence of each, then inspect rendered content and selected channels.
Expected
The personal occurrence has its declared console wording; the operational occurrence has its mapped Slack payload. Stored channel preferences do not activate additional personal channels.
Data
A suite-owned workspace, named staff accounts and unique occurrence keys; external adapters record attempts without shared writes.
Read the test, responsibility and provisioning declarations from the Platform manifest.
Steps
Validate the full manifest, inspect its declared keys and render every example through the real content checker.
Expected
The manifest contains the test declaration, four responsibility declarations and two provisioning declarations; all schemas and examples pass their checks.
Data
Pure declaration and example inputs in one process.