SpecificationsDuplicate Review and Record Merging
19 acceptance test sets for MOD-CRM-DQ, one per capability, holding 158 scenarios — 150 of them already bound to an existing test. A scenario names the rules and journey assertions it proves; it never restates them.
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-CRM-DQ-001 | Detect duplicate records after changes | 11 | 10 | 2 | 8 api · 2 unit · 1 browser | Proposed |
ATS-CRM-DQ-002 | Explain the strength of a duplicate suggestion | 9 | 9 | 1 | 8 unit · 1 browser | Proposed |
ATS-CRM-DQ-003 | Set the response to duplicate matches | 9 | 9 | 3 | 4 unit · 4 api · 1 browser | Proposed |
ATS-CRM-DQ-004 | Check drafts and account for block overrides | 8 | 8 | 4 | 7 api · 1 browser | Proposed |
ATS-CRM-DQ-005 | Refresh duplicate evidence across a record type | 7 | 5 | 3 | 6 api · 1 browser | Proposed |
ATS-CRM-DQ-006 | Reuse a contact during portal registration | 6 | 6 | 3 | 6 api | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-CRM-DQ-007 | Review duplicate groups in a shared queue | 8 | 8 | 2 | 2 unit · 5 api · 1 browser | Proposed |
ATS-CRM-DQ-008 | Dismiss false matches and reopen review | 8 | 8 | 2 | 6 api · 1 unit · 1 browser | Proposed |
ATS-CRM-DQ-009 | Record a duplicate that matching missed | 4 | 4 | 2 | 4 api | Proposed |
ATS-CRM-DQ-010 | Review and merge from a record page | 6 | 5 | 2 | 3 api · 3 browser | Proposed |
ATS-CRM-DQ-011 | Understand the duplicate-review workload | 4 | 3 | 1 | 3 api · 1 browser | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-CRM-DQ-012 | Prepare a merge and choose its survivor | 7 | 7 | 2 | 5 api · 1 unit · 1 browser | Proposed |
ATS-CRM-DQ-013 | Resolve differences in the merge preview | 10 | 10 | 4 | 1 unit · 8 api · 1 browser | Proposed |
ATS-CRM-DQ-014 | Preserve the right information on the surviving contact | 14 | 14 | 2 | 10 unit · 3 api · 1 browser | Proposed |
ATS-CRM-DQ-015 | Keep related records consistent through a merge | 9 | 9 | 2 | 5 api · 2 unit · 2 browser | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-CRM-DQ-016 | Execute the approved merge atomically | 14 | 13 | 5 | 9 api · 4 unit · 1 browser | Proposed |
ATS-CRM-DQ-017 | Combine organizations and their connections safely | 9 | 7 | 1 | 5 unit · 3 api · 1 browser | Proposed |
| Acceptance test set | Proves capability | Scenarios | Bound | Negative | Levels | Status |
|---|---|---|---|---|---|---|
ATS-CRM-DQ-018 | Resolve identities absorbed by a merge | 8 | 8 | 3 | 7 api · 1 browser | Proposed |
ATS-CRM-DQ-019 | Inspect merge outcomes and attribution | 7 | 7 | 2 | 6 api · 1 browser | Proposed |