<Backend engineer & Pact noob alert> Is it possible to run Pact within the jsdom environment? I'm trying to experiment with a contract test setup for our TS (old and janky) frontend. Specific error in this case is

FormData is not defined

when I run the test within the

node

env and

ReferenceError: setImmediate is not defined

when I run within jsdom. This later error seems to be an issue with Jest 27 and up, but I don't want to downgrade the Jest version.

Hey hey, https://docs.pact.io/implementation_guides/javascript/docs/troubleshooting#usage-with-jest https://github.com/pact-foundation/pact-js/blob/master/docs/troubleshooting.md#usage-with-jest 1.

npx -y pactman

2.

Pact

3.

jest

4.

<enter>

5. chefkiss

So I've tried the

/**
 * @jest-environment node
 */

which successfully switches the env to node I assume, as the reference error is gone). The problem is my test uses jsdom-specific code:

it('returns the correct response', (done) => {

      const formData = new FormData();
      formData.append(
        'file',
        'this is the file string',
        'this is the file name',
      );

I think jsdom code should work in a Pact test, so long as it runs in a node environment (because Pact needs it). Could you please share a bit more of the test? The main thing is, seeing how the request is sent to the API and how that can be redirected to Pact. Seeing

FormData

I’m assuming it’s going to be a multipart form post, which should be testable

yea, wrapping up for the holiday so will probably pick this up in the new year, thanks!