With Cypress, you can easily create tests for your modern web applications, debug them visually, and automatically run them in your continuous integration builds.

Cypress Community

hrmm, doesn't seem to be picking it up. (unless i'm doing it wrong!)

all of the docs talk about setting the env var before running cypress

(FYI, the ENV definitely works when i add it to my docker-compose)

not really getting anywhere with this. perhaps i'll put in a github issue for consideration

Thanks <@778685542110855199>, if it is not trivial, it's the best chance you have

I'm also happy to forward you to our e2e peeps. Bart and I are mostly Component Testing wizards

<@!363353019187724288> So since I've started migrating my component testing over to 7.0+, I realize that the E2E test runner doesn't work entirely. I get this error before a test even really starts, which I think may arise because we are no longer using the file:preprocessor

This, to be more clear. But I'm not exactly sure how to handle it, or maybe I misunderstand. I remember you saying that webpack-preprocessor dependency shouldn't be required, but could that depend on the Vue app?

My colleague feels like he remembers that he had to use the preprocessor to also get the e2e testing to work for our app. And it seems like that is true when I got back to our old setup and Cypress 6.8. Let me know if this doesn't make sense though.

I am on my mobile right now for a coffee run

ok, thanks. Np. I'm just trying a few more things to see if I can narrow it, but I think its close to the problem already at least.

preprocessors are actually used for more than component testing

CT was kind of exploiting a possibility enabled by preprocessors

https://docs.cypress.io/api/plugins/preprocessors-api

So even if they are not useful anymore for CT they can still be useful for e2e

And to make sure that e2e and CT do not bump into each other

1: create 2 cypress.json files and specify the --configFile or -C

Ok, does that mean I can add another 'on' call and add the previous arguments we had for that? In here:

I am looking for the documentation for the overrides

it does mean you could add another "on" call

Ok, I'm really not good at any of this stuff, so I might need more help =/

I would use the override to tell cypress that in component testing, it should use this plugins file