Product grid, several cards, each with an "Add" button. The context on our add-to-basket locator is:
{ role: 'button', name: 'Add', text: 'Add', description: 'add to basket' }The primary broke after a class rename. The healer found three matching buttons, scored the candidate above minScore anyway, took the first one and added the wrong product. The scenario passed, because the assertion afterwards only checks the basket count.
The event records count: 3, so the healer knew. I understand that uniqueness lowers the score rather than disqualifying the candidate, and that it resolves to the first match. What I would like to know is whether there is a supported way to say "refuse to heal when more than one thing matches", short of raising minScore far enough that non-unique candidates fall below it — which also takes out plenty of heals I do want.