If you have a file like that in your repo, I think you could just execute it with node.

node mocks/index.js

Oh, duh. Sorry... I've been looking at this way too long today and my brain is pretty fried...

Thats how you would handle it server side in the build. Then you would still have to start the client side mocks.

This is what I have used in the past to start client side mocks when Cypress is executed

Cypress.on("test:before:run:async", async () => { await worker.start(); });

clientside mocks we have a whole apparatus for already, it does use msw

Ah ok

bleh, hitting an `import`/`require` headache trying to

node

that script.

Oh lame, might have to break the server start one out into its own file so it can be executed in node and the client side mocks are executed elsewhere

I just swapped everything over to require and it looks like it worked. Any idea where this is running now?

Im not sure I understand the question

So my test app is fetching

cat-facts.com/api

or whatever, what's the mechanism to make the app hit MSW during build time instead of getting actual cat facts?

Like its not running on a localhost port somewhere as far as I can tell?

Actually I think my approach might be the wrong one to take here. I need to look into this more.

Never mind, another melting-brain moment.

if (process.env.NODE_ENV === 'test') {
  require('../../mocks')
}

high up in the nextjs app and it'll pick it up during the build process.

I think.

Well actually I think im wrong there.

Based on the Next.js example there, you dont have to execute that file manually.

Yeah, I think what you said is on the right track but I don't think you have to node run that file, just import it into the app.

huzzah.

I have a few more things I want to explore in this repo then I'll post the link, hopefully this can help someone else.

I am having a problem using request to authorise. looking at what is coming back after the request, body is empty. I think this may be due to the setup I have so hopefully someone can tell me. I have a frontend svelte app with a login screen. This calls the login rest api for a backend server and receives a token if the username / password is successful. Now when I login manually via the browser - success. When I use cypress to complete the screen - success. When I use cypress to call the login rest api directly - success. But if use request of the login page, then it doesn't work. So with the configuration above, is request just not going to work?

@gray-kilobyte-89541 please share how to handle websocket using cypress in angular app

I am not sure what difference it makes, but find my websocket advice by searching https://cypress.tips/search

I feel pretty dense here, but how do I turn on

experimentalInteractiveRunEvents

? I have tried both

module.exports = defineConfig({
  e2e: {
    ...
  },
  experiments: { experimentalInteractiveRunEvents: true }
})

and

module.exports = defineConfig({
  e2e: {
    ...,
    experiments: { experimentalInteractiveRunEvents: true }
  },
})

in my

cypress.config.js

file and I'm not see any logging output from either event.

Sorry, these are for the

before:spec

and

after:spec

event, I'm just trying to

console.log(spec)

.