Rhythm 2.0 Specifications

Appearance

ATS-CRM-DQ-011Understand the duplicate-review workload: Capability Test Specification

Markdown

ATS-CRM-DQ-011

Understand the duplicate-review workload: Capability Test Specification

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-CRM-DQ-011

Design

Executed by
TST-CRM-DQ-180, TST-CRM-DQ-182

KindAcceptance test setProduct areaCRMModuleDuplicate Review and Record MergingRevision1

Read atservices-crm a8d1364freact-console baf6dae3

Understand the duplicate-review workload: Capability Test Specification ​

Coverage ​

The rule matrix names the authored checks. A covered category means that a scenario exists; it does not report a passing execution. The coverage notes and findings identify missing checks, while execution sources retain the exact assertions inspected.

Required RuleScenarios
BR-CAP-CRM-DQ-011-01ATS-CRM-DQ-011-01, ATS-CRM-DQ-011-05
BR-CAP-CRM-DQ-011-02ATS-CRM-DQ-011-01, ATS-CRM-DQ-011-05
BR-CAP-CRM-DQ-011-03ATS-CRM-DQ-011-02, ATS-CRM-DQ-011-05
BR-CAP-CRM-DQ-011-05ATS-CRM-DQ-011-03, ATS-CRM-DQ-011-05
BR-CAP-CRM-DQ-011-06ATS-CRM-DQ-011-04, ATS-CRM-DQ-011-05

Open the overview and follow its counts. Complete a re-check, dismiss a group and execute one merge, then compare overview counts with group and merge listings.

These sequences test the handoffs named in the interaction coverage record. A proposed sequence remains unbound until an executable run checks its combined outcome; component assertions alone leave that obligation open.

Coverage

  • Rule covered
  • Transition gap: FND-CRM-DQ-062
  • Validation gap: FND-CRM-DQ-062
  • Permission covered
  • Edge gap: FND-CRM-DQ-062
  • Failure gap: FND-CRM-DQ-062
  • Boundary covered
  • Concurrency gap: FND-CRM-DQ-062
  • Invariant gap: FND-CRM-DQ-062
  • Interaction covered

Test Scenarios

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

01 Overview distinguishes records, pairs and group confidenceruleapitest
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
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 boundboundaryapitest
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
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 authoritypermissionapinegativetest
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
Source
services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#refuses the anonymous call
04 Console totals reconcile with the underlying workinteractionbrowserproposed
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
05 Background work and completed merges reconcile with the overviewinteractionapiproposed
Proves
BR-CAP-CRM-DQ-011-01 BR-CAP-CRM-DQ-011-02 BR-CAP-CRM-DQ-011-03 BR-CAP-CRM-DQ-011-05 BR-CAP-CRM-DQ-011-06
Preconditions
Run-owned contact and organization records, the relevant staff permissions and the related state described by the sequence.
Steps
Complete a re-check, dismiss a group and execute one merge, then compare overview counts with group and merge listings.
Expected
The overview agrees with the named workload and recent-history rules at the fixed observation time.
Data
An isolated workspace with related records and fixed timestamps; owned participant failure injection where requested.
Source
CAP-CRM-DQ-011; CAP-CRM-DQ-005; CAP-CRM-DQ-019; WF-CRM-DQ-001

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