Understand the duplicate-review workload: Acceptance Scenarios

Coverage

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

4 scenarios proving CAP-CRM-DQ-011; 3 bound to an existing test.

01 Overview distinguishes records, pairs and group confidenceapitest

Proves: BR-CAP-CRM-DQ-011-01 BR-CAP-CRM-DQ-011-02
Preconditions: Prepare two open contact groups, dismissed and confirmed pairs and an active contact re-check.
Steps: Read the summary.
Expected: Counts match the setup, groups use their strongest confidence, the run is active and the window contains no merges.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/integration/services/summary/duplicate-summary.integration.spec.js#counts the contact groups, the records in them and the pairs of each status
services-crm:modules/duplicates/tests/integration/services/summary/duplicate-summary.integration.spec.js#breaks the open groups down by band, the group taking the band of its strongest pair
services-crm:modules/duplicates/tests/integration/services/summary/duplicate-summary.integration.spec.js#says a rescan of the contacts is under way, so a reader knows the counts are being rebuilt
Source: services-crm:modules/duplicates/tests/integration/services/summary/duplicate-summary.integration.spec.js#counts the contact groups, the records in them and the pairs of each status

02 Capped totals identify a lower boundapitest

Proves: BR-CAP-CRM-DQ-011-03
Preconditions: Create more open pairs than the configured ceiling.
Steps: Request the summary.
Expected: The response returns the ceiling and marks both the record type and overall result capped.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/integration/services/summary/duplicate-summary.integration.spec.js#answers the CAP rather than the count, so no reader waits for a number nobody reads
services-crm:modules/duplicates/tests/integration/services/summary/duplicate-summary.integration.spec.js#says the record type is capped, so every number of it is read as a floor
services-crm:modules/duplicates/tests/integration/services/summary/duplicate-summary.integration.spec.js#says the overview as a whole is capped, which is what the page needs to know
Source: services-crm:modules/duplicates/tests/integration/services/summary/duplicate-summary.integration.spec.js#answers the CAP rather than the count, so no reader waits for a number nobody reads

03 Overview reads require authorityapinegativetest

Proves: BR-CAP-CRM-DQ-011-05
Preconditions: Use anonymous and permissionless callers.
Steps: Request the overview.
Expected: Both calls are denied.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#refuses the anonymous call
Source: services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#refuses the anonymous call

04 Console totals reconcile with the underlying workbrowserproposed

Proves: BR-CAP-CRM-DQ-011-06
Preconditions: Prepare open, dismissed and confirmed work plus a merge reaching thirty days old.
Steps: Open the overview and follow its counts.
Expected: Queue and list totals agree, and the old merge leaves the recent window at the boundary.
Data: The existing scenario setup supplies the required records.
Source: FND-CRM-DQ-031