Should mocks defined using matching().respond() clobber mocks from yesno.mock

[kevinmstephens]

See

yesno/test/unit/yesno.spec.ts

Line 660 in bac495a

it('should support mock override with respond', async () => {

If we defined mocks for calls to /A, /B, /C, yesno will try to match those 3 mocks in order of API calls made. If the 2nd API call, for example, isn't to /B it will error.

A user then adds matching('/X').respond() in addition to the mocks for A, B, C above. If the user then has API calls in this order:
A, B, X, C

They will encounter an error on the call to C b/c in fact X has replaced C so C mock will no longer exist.

In fact to get this to work I would have to:

• create mocks ``/A, /B`, `/DUMMY_TO_GET_CLOBBERED`, /C`.
• create matching('/X').respond()
• ✅ call A, B, X, C

No proposed updated API here. For now I just wanted to note this behavior and consider if it's what we want.