Rhythm 2.0 Specifications

Appearance

ATS-CRM-REG-010Identify placements that need recalculation: Acceptance Test Set

Markdown

ATS-CRM-REG-010

Identify placements that need recalculation: Acceptance Test Set

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-CRM-REG-010

KindAcceptance test setProduct areaCRMModuleRegionsRevision2

Read atservices-crm a8d1364freact-console baf6dae3

Test Scenarios

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

01 Policy saves preserve existing placementsapitest
Proves
BR-CAP-CRM-REG-010-01 AS-JNY-CRM-REG-001-01
Preconditions
Records were placed under an enabled older policy.
Steps
Save coverage that would choose different regions and read the records.
Expected
Their regions remain as previously stored.
Data
Contact records with existing regional values.
Bound to
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment.integration.spec.js#rule changes and the recalculation › changes no record when the rules are saved
services-crm:tests/e2e/dev/regions.dev.spec.ts#changes no contact when the rules are saved
Source
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment.integration.spec.js#rule changes and the recalculation › changes no record when the rules are saved
02 A successful current-generation run clears needapitest
Proves
BR-CAP-CRM-REG-010-02
Preconditions
Automatic placement is enabled.
Steps
Save rules, read settings, recalculate and read settings again.
Expected
Recalculation is needed after saving and no longer needed after successful current-policy processing.
Data
A single policy entry.
Bound to
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment-rules.integration.spec.js#whether a recalculation is needed › says a recalculation is needed once the rules have been saved and nothing has recalculated
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment-rules.integration.spec.js#whether a recalculation is needed › says none is needed once a recalculation has succeeded against those rules
services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.queries.integration.spec.js#the settings of a tenant that saved them › says a recalculation is needed, because the rules changed and none has run since
react-console:e2e/dev/regions.dev.spec.ts#asks for a recalculation after a rule changes, and stops asking once it has run
Source
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment-rules.integration.spec.js#whether a recalculation is needed › says a recalculation is needed once the rules have been saved and nothing has recalculated
03 Policy-affecting writes raise needapitest
Proves
BR-CAP-CRM-REG-010-03
Preconditions
A successful run covers the current policy.
Steps
Add a rule, recalculate and deactivate an enabled rule’s target.
Expected
The rule write and relevant deactivation each raise the need signal.
Data
A single policy entry.
Bound to
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment-rules.integration.spec.js#whether a recalculation is needed › says one is needed again as soon as a rule is added
Source
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment-rules.integration.spec.js#whether a recalculation is needed › says one is needed again as soon as a rule is added
04 Changes during processing remain outstandingapitest
Proves
BR-CAP-CRM-REG-010-04
Preconditions
A recalculation is running.
Steps
Add a rule, finish the run and inspect settings.
Expected
The settings still request recalculation.
Data
Record volume exceeding one processing batch.
Bound to
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment-rules.integration.spec.js#whether a recalculation is needed › a rule saved while a recalculation is under way › says one is still needed, because the run was recorded under the rules as they were before
Source
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment-rules.integration.spec.js#whether a recalculation is needed › a rule saved while a recalculation is under way › says one is still needed, because the run was recorded under the rules as they were before
05 Equal timestamps do not hide changesapitest
Proves
BR-CAP-CRM-REG-010-05
Preconditions
A completed run establishes a successful generation.
Steps
Add a rule with a timestamp equal to that run’s start.
Expected
The generation comparison still requests recalculation.
Data
A fixed clock for coincident timestamps.
Bound to
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment-rules.integration.spec.js#whether a recalculation is needed › a rule change stamped at the very instant the last run started › says one is needed after a rule is added at the very instant the run started
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment-rules.integration.spec.js#whether a recalculation is needed › a rule change stamped at the very instant the last run started › says none is needed while no rule has changed since that run
Source
services-crm:modules/regions/tests/integration/services/region-assignment/region-assignment-rules.integration.spec.js#whether a recalculation is needed › a rule change stamped at the very instant the last run started › says one is needed after a rule is added at the very instant the run started
06 Disabled or absent settings suppress needapitest
Proves
BR-CAP-CRM-REG-010-06
Preconditions
One workspace has no settings and another has disabled assignment.
Steps
Read both settings records.
Expected
Neither reports recalculation needed.
Data
Two distinct customer workspaces.
Bound to
services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.queries.integration.spec.js#a tenant that has saved no settings › says no recalculation is needed, because a tenant with no settings assigns nothing to recalculate
services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.queries.integration.spec.js#settings saved a second time › says no recalculation is needed, because the tenant assigns nothing automatically any more
Source
services-crm:modules/regions/tests/integration/services/persistence/region-assignment-settings.queries.integration.spec.js#a tenant that has saved no settings › says no recalculation is needed, because a tenant with no settings assigns nothing to recalculate
07 An unchanged save still raises needapiproposed
Proves
BR-CAP-CRM-REG-010-08
Preconditions
A successful run covers the current policy.
Steps
Save an identical settings replacement.
Expected
The change counter advances and recalculation becomes needed.
Data
An existing assignment configuration.
Source
services-crm:modules/regions/services/persistence/region-assignment-settings.ts:saveRegionAssignmentSettings

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software