ATS-CRM-DQ-002Explain the strength of a duplicate suggestion: Acceptance Scenarios
MarkdownExplain the strength of a duplicate suggestion: Acceptance Scenarios
Coverage
Test Scenarios
9 scenarios proving CAP-CRM-DQ-002; 9 bound to an existing test.
03 Organization evidence applies its weights and ceilingsunittest
- Proves
BR-CAP-CRM-DQ-002-03 - Preconditions
- Prepare each organization evidence type, a domain-only resemblance and an ancestor pair.
- Steps
- Score the fixtures.
- Expected
- Points follow the schedule, domain-only resemblance caps at 69 and ancestry at 35.
- Data
- The existing scenario setup supplies the required records.
- Bound to
- Source
- services-crm:modules/duplicates/tests/unit/services/matching/bands.spec.js#declares the weight of every row of §5.2
04 Band boundaries distinguish stored suggestionsunittest
- Proves
BR-CAP-CRM-DQ-002-04 - Preconditions
- Use scores 0, 34, 35, 49, 50, 69, 70, 89, 90 and 100.
- Steps
- Resolve the confidence band for each score.
- Expected
- Values below 35 have no band; the remaining boundaries produce low, medium, high and very high correctly.
- Data
- The existing scenario setup supplies the required records.
- Bound to
- Source
- services-crm:modules/duplicates/tests/unit/services/matching/bands.spec.js#gives 34 no band at all, so the pair is not stored
05 Reasons explain points before score ceilingsunittest
- Proves
BR-CAP-CRM-DQ-002-05 - Preconditions
- A pair contains several evidence contributions and a score limit.
- Steps
- Render the explanation.
- Expected
- Reasons follow scoring order with their points, followed by the ceiling explanation.
- Data
- The existing scenario setup supplies the required records.
- Bound to
- Source
- services-crm:modules/duplicates/tests/unit/services/matching/explanation.spec.js#renders one sentence per piece of evidence, in the order the scorer found it
06 Explanations mask private matching valuesunitnegativetest
- Proves
BR-CAP-CRM-DQ-002-06 - Preconditions
- A pair agrees on e-mail, phone and birth date.
- Steps
- Generate the masked evidence explanation.
- Expected
- E-mail retains only its first character and domain, phone its last four digits and no full birth date appears.
- Data
- The existing scenario setup supplies the required records.
- Bound to
- Source
- services-crm:modules/duplicates/tests/unit/services/matching/explanation.spec.js#never carries a full e-mail address into a sentence
09 Evidence totals remain boundedunittest
- Proves
BR-CAP-CRM-DQ-002-13 - Preconditions
- Prepare pairs with excess positive evidence and conflicting evidence.
- Steps
- Score each pair and inspect the final total and applied ceilings.
- Expected
- Totals remain between zero and 100 and respect the lowest ceiling.
- Data
- Use the records and caller described in this scenario.
- Bound to
- Source
- services-crm:modules/duplicates/services/matching/scoring.ts:scoreOf