ATS-CRM-REG-002Retire regions while preserving their references: Acceptance Test Set
MarkdownRetire regions while preserving their references: Acceptance Test Set
Coverage
Test Scenarios
6 scenarios proving CAP-CRM-REG-002; 4 bound to an existing test.
03 Delete authority is separate from edit authoritybrowsernegativetest
- Proves
BR-CAP-CRM-REG-002-03 - Preconditions
- A user can create and update regions but cannot delete them.
- Steps
- Request removal through the service and inspect the region menu.
- Expected
- Deletion requires the delete key and the menu supplies no usable Delete action.
- Data
- An ordinary user-tier identity.
- Bound to
- Source
- services-crm:tests/unit/regions-authorization.spec.ts#requires crm.regions.delete to delete a region
04 Ordinary replacement can alter a delete lockapinegativeproposed
- Proves
BR-CAP-CRM-REG-002-04 BR-CAP-CRM-REG-002-05 - Preconditions
- One region has a delete lock and another has a full lock.
- Steps
- Delete the first, replace the second and replace the first without its lock.
- Expected
- Deletion and the full-lock update are refused; the ordinary replacement clears the delete lock.
- Data
- Regional examples with deletion and full locks.
- Source
- services-crm:modules/regions/services/persistence/regions.ts:updateRegionRow, deleteRegionRow
05 Deactivation distinguishes referenced targetsapiproposed
- Proves
BR-CAP-CRM-REG-002-07 - Preconditions
- Assignment is enabled and the current generation has a successful run.
- Steps
- Deactivate a target of an enabled rule and read settings; repeat with an unreferenced region.
- Expected
- The referenced target raises recalculation need and the unrelated deactivation records no policy change.
- Data
- A pair of regional definitions and one policy entry.
- Source
- FND-CRM-REG-021