ATS-CRM-REG-005Maintain individual rules alongside the shared policy: Acceptance Test Set

ATS-CRM-REG-005

Maintain individual rules alongside the shared policy: Acceptance Test Set

KindAcceptance test setProduct areaCRMModuleRegionsRevision2

Read atservices-crm a8d1364freact-console baf6dae3

Maintain individual rules alongside the shared policy: Acceptance Test Set

Coverage

Show evidence (sources, provenance, origins, pinned commits)

7 scenarios proving CAP-CRM-REG-005; 6 bound to an existing test.

01 Insertion supports append and earlier placementapitest

Proves: BR-CAP-CRM-REG-005-01
Preconditions: Two rules occupy consecutive positions.
Steps: Create without a position and then create at the first position.
Expected: The first appends; the second precedes the others, which retain a consecutive order.
Data: A two-entry assignment policy.
Bound to: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#appends a created rule at the end of the order
services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#lists both rules in the order they are tried
Source: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#appends a created rule at the end of the order

02 Individual editing checks its versionapinegativeproposed

Proves: BR-CAP-CRM-REG-005-02
Preconditions: A rule has version two.
Steps: Replace with version one, omit the replacement version and patch with the current version test.
Expected: The stale and missing versions are rejected while the current patch succeeds.
Data: A single policy entry.
Source: FND-CRM-REG-022

03 Deletion closes the position gapapitest

Proves: BR-CAP-CRM-REG-005-04
Preconditions: The policy contains two rules.
Steps: Remove the first rule.
Expected: The retained rule occupies the first position.
Data: A two-entry assignment policy.
Bound to: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#deletes a rule
services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#closes the gap the delete left, so the rule that remains is at the first position
Source: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#deletes a rule

04 Reorder requires the complete distinct setapinegativetest

Proves: BR-CAP-CRM-REG-005-05
Preconditions: Two identified rules exist.
Steps: Submit incomplete, duplicate and unknown-containing orders, then the valid reversed order.
Expected: Invalid orders identify their problems and preserve order; the valid order reverses the sequence.
Data: A two-entry assignment policy.
Bound to: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#answers 400 for an order that does not name every rule of the tenant
services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#puts the rules in the order the body names, renumbering the positions
Source: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#answers 400 for an order that does not name every rule of the tenant

05 Individual writes invalidate older policy draftsapinegativetest

Proves: BR-CAP-CRM-REG-005-06
Preconditions: A client reads settings at version four.
Steps: Create a rule and submit the older whole-list draft.
Expected: The settings version advances and the older draft conflicts without dropping the new rule.
Data: An existing assignment configuration.
Bound to: services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.integration.spec.js#rules written one at a time, beside a settings save › moves the settings’ version once for each rule written, as a settings save does
services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.integration.spec.js#rules written one at a time, beside a settings save › a whole-list save read before a rule was created › is refused as stale, so the new rule is not dropped
services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.integration.spec.js#rules written one at a time, beside a settings save › a whole-list save read before a rule was created › leaves the rule created beside it in the list
Source: services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.integration.spec.js#rules written one at a time, beside a settings save › moves the settings’ version once for each rule written, as a settings save does

06 Enabled assignment tolerates removal of its final ruleapitest

Proves: BR-CAP-CRM-REG-005-09
Preconditions: The policy has one enabled rule.
Steps: Disable and then remove that rule.
Expected: The requests succeed and assignment remains enabled with no rules.
Data: A single policy entry.
Bound to: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#the last enabled rule while assignment is on › disables it, leaving the tenant assignment on with nothing to match
services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#the last enabled rule while assignment is on › deletes it
services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#the last enabled rule while assignment is on › leaves assignment on, so the console’s switch stays usable with no rule
Source: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#the last enabled rule while assignment is on › disables it, leaving the tenant assignment on with nothing to match

07 Rule reads cannot cross workspacesapinegativetest

Proves: BR-CAP-CRM-REG-005-11
Preconditions: Separate workspaces hold rules.
Steps: List through the other workspace and request an unknown rule.
Expected: No foreign rule appears and the unknown read returns not found.
Data: Two distinct customer workspaces.
Bound to: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#the rules, one at a time › answers none of this tenant's rules to another tenant's list
services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#answers 404 for a rule the tenant does not have
Source: services-crm:modules/regions/tests/e2e/regions.e2e.spec.js#the rules, one at a time › answers none of this tenant's rules to another tenant's list