#1173 Improve developer experience around consumer pact testing Issue created by dsteinbach-ep Before making a feature request, I have: ☑︎ Searched the issues to check that this feature hasn't been requested before ☑︎ Checked the documentation to see if it is possible to do what I want already Description I couldn't find any discussions about this so I apologize if I missed a critical bit of information that tells me why this is a bad idea. Also, this feature request might be better suited for another repo but I'm not sure if other packages have the same limitations im facing with Pact.js, which is... I feel like certain design choices of Pact creates a bad developer experience which severely limiting Pacts adoption. Problem To start off, I believe unit tests are an ideal place to create your consumer pact tests because: • They are low on the testing pyramid and faster to run than E2E tests. • They are "closer to the metal" therefore having better API coverage. • We are already mocking API request/responses in these files so why duplicate that effort elsewhere? However... • Developers need to wait for mock servers to spin up (and destroyed) per test case which is painfully slow. This speed penalty alone prevents Pact adoption for unit tests. • Many unit tests test more than a single consumer/provider relationship, however, while it is possible to define multiple pacts per test mock server initialization requires nested synchronous calls (slow and inelegant). Overall, the fact you have to setup your interactions BEFORE running the mock server seems to be the crux of all these problems. Possible Solution First, mock servers are initialized as soon as consumer/provider relationships are defined during Pact initialization. These mock servers should be long running, created in a global unit test setup and destroyed in a global tear down (if they are not already child processes of the test runner). Something like: jest.config.js

{
   setupFiles: ['<rootDir>/test/initializePact.ts'],
}

test/pacts.ts

export const productServicePact = new PactV4({
  consumer: 'user-service',
  provider: 'product-service',
});

export const orderServicePact = new PactV4({
  consumer: 'user-service',
  provider: 'order-service',
});

test/initializePact.ts

import { produtServicePact, orderServicePact } from './pacts';

productServicePact.startServer((url) => {
   process.env.PRODUCT_SERVICE_URL = url;
});

orderServicePact.startServer((url) => {
   process.env.ORDER_SERVICE_URL = url;
});

Secondly, interactions (request/response pairs) should be defined per test case and automatically cleared before the next case is ran (writing contract files as it goes). Something like:

it('verifies some state', () => {
   withInteractions([orderServiceInteraction1, productServiceInteraction1, productServiceInteraction2], async () => {
      const userId = 123;
      const response = await productService.getRecommended(userId);
      ... etc ...
      expect(...).toBe(true);
   });
});

With this we wouldn't need dedicated Pact-only unit or e2e tests. It would just be part of how we already mock server request/responses. The time penalty would be minimal and be a completely ergonomic developer experience. Just my thoughts. I'm pretty new to Pact testing and I am really excited by the value it offers. Hopefully, this wasn't me just completely missing the Pact's intended use. Thanks! pact-foundation/pact-js