Hi all, I’ve been using typescript to write ‘happy path’ PACT tests without any problem using a pattern like this:

// PACT test for getBasketById
describe('Given we are requesting specific basket', () => {
  test('When a basket exists', async () => {
    // set up Pact interaction
    await provider.addInteraction({
      state: 'When the basket exists',
      uponReceiving: 'get the specified basket',
      withRequest: interactionRequest.GET_BASKET,
      willRespondWith: interactionResponse.BASKET_NORMAL_RESPONSE,
    });

    // make request to PACT mock server
    await getData(provider.mockService.baseUrl + '/basket/' + OK_BASKET_ID);
  });

Now that I’m attempting error path tests (the response status is 404) I get the following error

thrown: Object {
   "errorCode": "BS-002",
   "errorMessage": "No basket has been found",
  }

    111 |   // Failed PACT test for getBasketById
    112 |   describe('Given we are requesting specific basket', () => {
  > 113 |     test('When the basket does not exists', async () => {
        |     ^
    114 |       // set up Pact interaction
    115 |       await provider.addInteraction({
    116 |         state: 'basket does not exists',

My code for the ‘error path’ test is as follows:

// Failed PACT test for getBasketById
describe('Given we are requesting specific basket', () => {
  test('When the basket does not exists', async () => {
    // set up Pact interaction
    await provider.addInteraction({
      state: 'basket does not exists',
      uponReceiving: 'get specified basket',
      withRequest: {
        method: HTTPMethod.GET,
        path: '/basket/' + BAD_BASKET_ID,
      },
      willRespondWith: {
        status: 404,
        headers: { 'Content-Type': 'application/json' },
        body: {
          errorCode: 'BS-002',
          errorMessage: 'No basket has been found',
        },
      },
    });

    // make request to Pact mock server
    await getData(provider.mockService.baseUrl + '/basket/' + BAD_BASKET_ID);
  });
});

How do I handle the thrown object? PS: If I change the response status in my code to 200 then the problem disappears - but that’s obviously not what I’m after.

are you using axios for a client?

No. I'm using Fetch

what happens in your client code when you get a non 2xx response

Thanks

You can also see an example via our workshop https://github.com/pact-foundation/pact-workshop-js/blob/062ac903a1ca8184e2e3c536e429a953fd9c5890/consumer/src/api.pact.spec.js#L192

Yeh, I never got that to work 😕

hmm, love for you to elaborate when you have time. I have ran that workshop so many times, and do have some niceties that I want to address and get some tests into the repo but it definitely works, possibly not quite OOB because of all things dependencies I believe it was refreshed as part of the CI/CD workshop which I think is maybe a more reliable path at the moment, the workshops are on my growing list of things to look at

The issue is that http clients tend to throw when they get error status codes. Try/catch or using the JS test framework specific error handing (as above). This isn't a pact specific problem, so hopefully should be quite googleable

Hi @Yousaf Nabi (pactflow.io) /@Matt (pactflow.io / pact-js / pact-go), thanks for your help.....again 😁

👍