Review duplicate groups in a shared queue: Acceptance Scenarios

Coverage

Required Rule	Acceptance Scenario
`BR-CAP-CRM-DQ-007-01`	`ATS-CRM-DQ-007-01`, `ATS-CRM-DQ-007-08`
`BR-CAP-CRM-DQ-007-02`	`ATS-CRM-DQ-007-02`, `ATS-CRM-DQ-007-08`
`BR-CAP-CRM-DQ-007-03`	`ATS-CRM-DQ-007-03`
`BR-CAP-CRM-DQ-007-04`	`ATS-CRM-DQ-007-04`
`BR-CAP-CRM-DQ-007-05`	`ATS-CRM-DQ-007-05`, `ATS-CRM-DQ-007-08`
`BR-CAP-CRM-DQ-007-06`	`ATS-CRM-DQ-007-05`, `ATS-CRM-DQ-007-08`
`BR-CAP-CRM-DQ-007-07`	`ATS-CRM-DQ-007-06`, `ATS-CRM-DQ-007-08`
`BR-CAP-CRM-DQ-007-09`	`ATS-CRM-DQ-007-07`

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

Test Scenarios

8 scenarios proving CAP-CRM-DQ-007; 8 bound to an existing test.

01 Oversize connections identify their boundunittest

Proves: BR-CAP-CRM-DQ-007-01
Preconditions: Connect eleven records in a chain.
Steps: Build the duplicate grouping.
Expected: A displayed group contains ten records and reports that it is bounded.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/unit/services/groups/group-components.spec.js#holds at most ten records, so a group can always be merged as it is
services-crm:modules/duplicates/tests/unit/services/groups/group-components.spec.js#says the group it cut short is bounded, so a reader knows there may be more of it
Source: services-crm:modules/duplicates/tests/unit/services/groups/group-components.spec.js#holds at most ten records, so a group can always be merged as it is

02 Group identities survive structural changesunittest

Proves: BR-CAP-CRM-DQ-007-02
Preconditions: Start with a two-record group.
Steps: Grow, split, join and reduce its connected records.
Expected: Growth keeps identity, the largest split and join contribution retain it and an isolated record removes the group.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/unit/services/groups/group-components.spec.js#KEEPS the id the group already had, so the console is still looking at the same group
services-crm:modules/duplicates/tests/unit/services/groups/group-components.spec.js#keeps the id for the part holding MORE of the group’s records, the other part being a new group
services-crm:modules/duplicates/tests/unit/services/groups/group-components.spec.js#keeps the id of the group that contributed the MOST records, which is the one most reviewers were looking at
services-crm:modules/duplicates/tests/unit/services/groups/group-components.spec.js#is no group at all: a group holds at least two records
Source: services-crm:modules/duplicates/tests/unit/services/groups/group-components.spec.js#KEEPS the id the group already had, so the console is still looking at the same group

03 Pair and group writes share their commitapitest

Proves: BR-CAP-CRM-DQ-007-03
Preconditions: Prepare a batch that creates candidates.
Steps: Execute detection.
Expected: Stored pairs point to existing groups produced in the same transaction.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/integration/services/detection/duplicate-detection.integration.spec.js#grouped every pair it stored, the groups of a batch being written in the pass’s own transaction (§14)
Source: services-crm:modules/duplicates/tests/integration/services/detection/duplicate-detection.integration.spec.js#grouped every pair it stored, the groups of a batch being written in the pass’s own transaction (§14)

04 Confirmed decisions leave the grouped queueapitest

Proves: BR-CAP-CRM-DQ-007-04
Preconditions: Manually confirm a pair.
Steps: Recalculate groups.
Expected: The confirmed pair has no group reference.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-groups.integration.spec.js#belongs to no group: a confirmed pair is a decision, not a question the queue asks
Source: services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-groups.integration.spec.js#belongs to no group: a confirmed pair is a decision, not a question the queue asks

05 Queue parameters reject unsupported requestsapinegativetest

Proves: BR-CAP-CRM-DQ-007-05 BR-CAP-CRM-DQ-007-06
Preconditions: Prepare several groups.
Steps: Filter and page them, then change sort with an old cursor and supply unknown evidence.
Expected: Supported filters return matching pages; the incompatible cursor and unknown evidence are refused.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#answers only the groups of the band asked for or above it
services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#answers only the groups holding a pair that carries the evidence asked for
services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#refuses a cursor answered for another order, rather than paging in the wrong one
services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#refuses an evidence code no pair can carry, naming it rather than answering an empty page
Source: services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#answers only the groups of the band asked for or above it

06 Prefix search narrows groupsapitest

Proves: BR-CAP-CRM-DQ-007-07
Preconditions: Create groups with recognizable record names.
Steps: Search a valid prefix and an unmatched prefix.
Expected: Only the first search returns its matching groups.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#answers only the groups the records of a typed prefix are in, which is the search box
services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#answers nothing for a prefix no record of the tenant begins with
Source: services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#answers only the groups the records of a typed prefix are in, which is the search box

07 Queue access respects authority and existenceapinegativetest

Proves: BR-CAP-CRM-DQ-007-09
Preconditions: Use anonymous and permissionless callers and an absent group identity.
Steps: List groups and open that group.
Expected: Unauthorized reads fail and the absent group is not found.
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, the queue being the tenant’s own
services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#refuses a caller without the duplicates read permission
services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#answers 404 for a group this tenant does not have
Source: services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#refuses the anonymous call, the queue being the tenant’s own

08 A shared review address restores the locationbrowsertest

Proves: BR-CAP-CRM-DQ-007-01 BR-CAP-CRM-DQ-007-02 BR-CAP-CRM-DQ-007-05 BR-CAP-CRM-DQ-007-06 BR-CAP-CRM-DQ-007-07
Preconditions: Prepare several duplicate groups.
Steps: Sort, search surname prefixes and numbers, filter evidence, page and share an opened group.
Expected: The recipient opens the same selected group.
Data: The existing scenario setup supplies the required records.
Bound to: react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0233.spec.ts#CRM-ACC-0233
react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0273.spec.ts#CRM-ACC-0273
react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0275.spec.ts#CRM-ACC-0275
Source: react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0233.spec.ts#CRM-ACC-0233

Planning

Review duplicate groups in a shared queue: Acceptance Scenarios ​

Coverage ​

Test Scenarios

Review duplicate groups in a shared queue: Acceptance Scenarios

Coverage