The category map separates specified cases from recorded gaps. A proposed case describes proof to implement; a binding identifies the assertions supplied by an existing executable file. The permission and transition ledgers record the individual checks needed for the capability.
The interaction scenarios exercise save corrections without overwriting another change; remove records and their owned information; inspect a record’s changes over time; configure affiliation types and contact roles; organize the workspace’s record classifications. They change one part of a prepared record and inspect the dependent outcome. Unbound interactions remain proposed rather than implying an existing end-to-end implementation.
The frontmatter pins the repositories and identifies the source anchors for each scenario. Bindings record inspected assertions, while unbound cases remain proposed. Source inspection supplies no execution result or product approval.
Coverage
Rulecovered
Transitioncovered
Validationgap: FND-CRM-ENT-063
Permissioncovered
Edgecovered
Failuregap: FND-CRM-ENT-063
Boundarycovered
Concurrencygap: FND-CRM-ENT-063
Invariantcovered
Interactioncovered
Test Scenarios
16 scenarios proving CAP-CRM-ENT-015; 8 bound to an existing test.
01Lock and unlock need their own administrator keyspermissionbrowsernegativetest
Run-owned unlocked contact and organization records are available to a lock operator.
Steps
For each record, apply delete lock, strengthen to full lock, weaken to delete lock and release it. On another record, apply full lock directly and release it. Read the current version before each action and inspect both audits.
Expected
Every changed lock advances its owner version and contributes a reasoned audit; reads reflect each requested lock state.
Data
Run-owned records and configuration in an isolated workspace.
An eligible record and configuration fixture exist for each operation; the caller can reach only the run’s workspace.
Steps
For each declared permission, execute its matching operation with that permission, then without it while retaining the other required grants. Read affected records after every refused mutation.
Expected
The authorized case reaches the operation; the missing-grant case is refused and preserves saved data. Record access alone does not authorize the other declared actions.
Data
Run-owned records and configuration in an isolated workspace.