Ah, I think executetest needs to be called on the return of the addinteraction block (it's a builder so executetest is only available after the setup has been completed) Which example have you used, it needs updating

Looks like it is this example from consumer docs https://docs.pact.io/implementation_guides/javascript/docs/consumer#example source https://github.com/pact-foundation/pact-js/blob/master/docs/consumer.md#example which has probably been modified from the v2 example https://github.com/pact-foundation/pact-js/blob/master/examples/typescript/test/get-dog.spec.ts I can’t see the equiv v3/v4 example for that specific example @Александр Чепрасов - You can see the pattern Matt is referring to, in use here in the v4 tests https://github.com/pact-foundation/pact-js/blob/fced80ba02b6bdc566625adbf114105514e6e9ce/examples/v4/matchers/consumer.spec.ts#L27-L45 Matt is that only the case for the v4 interface being a builder interface ( I believe so) , we have the same layout in the docs example in this v3 test https://github.com/pact-foundation/pact-js/blob/master/examples/v3/typescript/test/user.spec.ts#L30-L43typescript/test/user.spec.ts#L30-L43

Yeah I think it's just V4. It forces you to call the prerequisites first