I guess I was expecting matchers to behave similarly as they do in Rspec

to match

with the same resolution as

to be_a(String)

nesting

The matchers get applied when the provider side test runs. I.e. They are for matching the response of a provider - this is a consumer test so matchers on the response won't yet have any effect

Got it. This makes sense. I was trying to figure out from JS documentation for an

any

matcher since I didn’t want to write a huge payload that I wasn’t testing for.