Review and merge from a record page: Acceptance Scenarios

Coverage

Test Scenarios

6 scenarios proving CAP-CRM-DQ-010; 5 bound to an existing test.

01 Candidate reads distinguish connected and isolated recordsapitest

Proves: BR-CAP-CRM-DQ-010-01
Preconditions: Prepare a candidate pair and an isolated record.
Steps: Read their per-record candidates.
Expected: The connected record returns its pair; the isolated record returns an empty list without a group.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#answers one record’s candidates, which is the banner its page shows
services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#answers nothing for a record in no pair at all
Source: services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#answers one record’s candidates, which is the banner its page shows

02 Per-record results include indirect group membersapitest

Proves: BR-CAP-CRM-DQ-010-02
Preconditions: A chain connects four records through three pairs.
Steps: Read candidates from one end.
Expected: The response names all four group records.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/duplicates/tests/integration/services/candidates/duplicate-candidate-view.integration.spec.js#answers the four records of that group, which is the banner a record page shows
Source: services-crm:modules/duplicates/tests/integration/services/candidates/duplicate-candidate-view.integration.spec.js#answers the four records of that group, which is the banner a record page shows

03 An absorbed record reports its destinationapinegativetest

Proves: BR-CAP-CRM-DQ-010-03
Preconditions: A contact has been merged away.
Steps: Read candidates using its old identity.
Expected: The response identifies the survivor as a merge destination rather than returning an empty list.
Data: The existing scenario setup supplies the required records.
Bound to: services-crm:modules/merges/tests/e2e/merged-records.e2e.spec.js#answers 410 to the old id’s duplicate candidates, rather than an empty list
Source: services-crm:modules/merges/tests/e2e/merged-records.e2e.spec.js#answers 410 to the old id’s duplicate candidates, rather than an empty list

04 Record alerts omit weak evidencebrowserproposed

Proves: BR-CAP-CRM-DQ-010-04
Preconditions: A record has very-high, medium and low pairs.
Steps: Open its page and an isolated record page.
Expected: Likely and possible sections include the stronger pairs, exclude low evidence and show no empty-record alert.
Data: The existing scenario setup supplies the required records.
Source: react-console:components/duplicates/indicator/use-record-duplicates.ts:useRecordDuplicates

05 Duplicate access is independent of ordinary record readingbrowsernegativetest

Proves: BR-CAP-CRM-DQ-010-05
Preconditions: Prepare a record reader without duplicate authority and a standard caller.
Steps: Open record and Data Quality pages and call duplicate APIs.
Expected: The restricted reader sees no duplicate indicator or Data Quality access, and unauthorized API requests fail.
Data: The existing scenario setup supplies the required records.
Bound to: react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0239.spec.ts#CRM-ACC-0239
Source: react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0239.spec.ts#CRM-ACC-0239

06 Record-page selections launch the same merge workspacebrowsertest

Proves: BR-CAP-CRM-DQ-010-06
Preconditions: A record has detected look-alikes.
Steps: Select matches and launch Merge With Selected, then use the More action.
Expected: Both launch the wizard with the intended records, no forced current-record survivor and a return to the entry location.
Data: The existing scenario setup supplies the required records.
Bound to: react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0286.spec.ts#CRM-ACC-0286
Source: react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0286.spec.ts#CRM-ACC-0286