Rhythm 2.0 Specifications

Appearance

ATS-CRM-DQ-008Dismiss false matches and reopen review: Acceptance Scenarios

Markdown

ATS-CRM-DQ-008

Dismiss false matches and reopen review: Acceptance Scenarios

Markdown
  • DocumentProposed

Planning

Proves capability
CAP-CRM-DQ-008

KindAcceptance test setProduct areaCRMModuleDuplicate Review and Record MergingRevision1

Read atservices-crm a8d1364freact-console baf6dae3

Test Scenarios

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

01 Dismissal retains attribution and the reviewed evidenceapitest
Proves
BR-CAP-CRM-DQ-008-01
Preconditions
An open pair awaits review.
Steps
Dismiss it using a note padded with spaces.
Expected
The stored dismissal has trimmed note, author, time and fingerprint and moves from open to dismissed work.
Data
The existing scenario setup supplies the required records.
Bound to
services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#dismisses the pair, stamping who said so, when, and the note as trimmed
services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#records the evidence the dismissal was made against, which a later score is compared with
services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#answers the stored group the dismissed pair has just joined, so a console needs no second request to show it
Source
services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#dismisses the pair, stamping who said so, when, and the note as trimmed
02 Repeated dismissal preserves the first reviewerapitest
Proves
BR-CAP-CRM-DQ-008-02
Preconditions
Prepare a dismissed pair and group.
Steps
Dismiss both again.
Expected
Both succeed without writes and retain the earlier identity, permitted name, time and note.
Data
The existing scenario setup supplies the required records.
Bound to
services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#tells the second request the pair was already dismissed, with the earlier who, when and note (D-34)
services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-candidates.integration.spec.js#is one decision however many times it is made: the second dismissal changes nothing stored
services-crm:modules/duplicates/tests/e2e/duplicate-groups.e2e.spec.js#answers a second dismissal of the dismissed group 200, saying it was already dismissed (D-34)
Source
services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#tells the second request the pair was already dismissed, with the earlier who, when and note (D-34)
03 A group decision commits all pairs togetherapitest
Proves
BR-CAP-CRM-DQ-008-03
Preconditions
A group has two open pairs and a failure-injection variant.
Steps
Submit group dismissal.
Expected
The normal request settles both with shared attribution and returns the dismissed group; failure settles neither.
Data
The existing scenario setup supplies the required records.
Bound to
services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-candidates.integration.spec.js#stamps one actor and one instant on all of them, which is the batch its undo takes back
services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-candidates.integration.spec.js#records against each pair the evidence that pair rested on, not the group’s
services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-candidates.integration.spec.js#leaves no pair of the group dismissed, a group being decided about whole or not at all
Source
services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-candidates.integration.spec.js#stamps one actor and one instant on all of them, which is the batch its undo takes back
04 Group undo preserves independent dismissalsapinegativetest
Proves
BR-CAP-CRM-DQ-008-04
Preconditions
Dismiss one pair separately and another through its group.
Steps
Undo the group decision twice.
Expected
Only the group-decided pair reopens and the second undo is refused.
Data
The existing scenario setup supplies the required records.
Bound to
services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-candidates.integration.spec.js#leaves the pair somebody dismissed on its own dismissed, that being a decision of its own
services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-candidates.integration.spec.js#refuses an undo of a group with no dismissed pair, rather than reporting one it did not make
Source
services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-candidates.integration.spec.js#restores exactly the pairs that one dismissal dismissed
05 Pair restoration clears dismissal metadataapitest
Proves
BR-CAP-CRM-DQ-008-05
Preconditions
A pair is dismissed.
Steps
Restore it twice.
Expected
It stays open with its score, without dismissal attribution or fingerprint, and the repeated restore is harmless.
Data
The existing scenario setup supplies the required records.
Bound to
Source
services-crm:modules/duplicates/tests/integration/services/persistence/duplicate-candidates.integration.spec.js#takes the whole dismissal off: who, when, why and on what evidence
06 Only new strong evidence reopens a dismissalunittest
Proves
BR-CAP-CRM-DQ-008-06
Preconditions
An existing pair is dismissed.
Steps
Correct a name typo and then add a shared phone.
Expected
The typo leaves the decision intact; the new phone reopens it with an explanation.
Data
The existing scenario setup supplies the required records.
Bound to
services-crm:modules/duplicates/tests/unit/services/matching/fingerprint.spec.js#leaves a pair dismissed when a name typo is fixed and nothing strong changes
services-crm:modules/duplicates/tests/integration/services/detection/duplicate-detection.integration.spec.js#says it reopened the dismissal, the pair now resting on evidence the dismissal did not see
Source
services-crm:modules/duplicates/tests/unit/services/matching/fingerprint.spec.js#leaves a pair dismissed when a name typo is fixed and nothing strong changes
07 Review authority controls decisionsapinegativetest
Proves
BR-CAP-CRM-DQ-008-09
Preconditions
Prepare reader and reviewer callers.
Steps
Attempt dismissal and restoration as both.
Expected
The reviewer succeeds and the reader is refused.
Data
The existing scenario setup supplies the required records.
Bound to
services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#answers 403 to that reader dismissing a pair, which is a decision and not a read
services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#answers 403 to that reader restoring a pair
services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#lets a reviewer dismiss a pair, which is the permission that decision asks for
Source
services-crm:modules/duplicates/tests/e2e/duplicates.e2e.spec.js#answers 403 to that reader dismissing a pair, which is a decision and not a read
08 Review decisions stay coherent across console entry pointsbrowsertest
Proves
BR-CAP-CRM-DQ-008-01 BR-CAP-CRM-DQ-008-03 BR-CAP-CRM-DQ-008-04 BR-CAP-CRM-DQ-008-06 BR-CAP-CRM-DQ-008-09
Preconditions
Prepare a four-record group and a record-page candidate.
Steps
Dismiss and undo the group, remove a member, dismiss and restore a noted pair, then introduce a shared mobile.
Expected
Dismissed work shows attribution, restoration clears it, new mobile evidence reopens the pair and read-only staff receive no decision controls.
Data
The existing scenario setup supplies the required records.
Bound to
Source
react-console:acceptance/crm/playwright/journeys/merging/CRM-ACC-0234.spec.ts#CRM-ACC-0234

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