Question on provider.verify() in consumer test? about pact-js HOT 4 CLOSED

Thanks @MichaelSu1983, perhaps our documentation is not very clear on this.

The provider.verify() step is key to the Pact tests. Verify checks that the interactions you've registered and expected to be present were in fact called by the function you were testing (e.g. it('POST', ...)).

Without it, you are registering expectations and creating a contract with those expectations in it, but you aren't sure if your code is actually a) calling the API(s) or b) sending the right data or c) using the data that is coming back. This is marginally better than pure documentation.

from pact-js.

Thanks @mefellows for the confirmation. Now I see.

So one more thing, is the way I structure tests correct?

should I return provider.verify() like the example, or leave "it('successfully verifies', () => provider.verify());" as separate test? or I can write it in one case "afterEach(() => provider.verify());"?

from pact-js.

It's a promise so you return it or explicitly complete it or you might not get the feedback if it passed or failed.

In terms of where it should go, It's up to you really, and your style.

It's probably nicer to have the verify() called in the same test scope so you know if it fails which test it relates to but some people like to keep them separate for readability etc.

from pact-js.

I understand the confusion here. I think we need to explain it better in the example and the docs.

from pact-js.