So I got past the webpack preprocessor error with the 2 plugins files and the right config in cypress.json. But now I have this issue where the Cypress testing library functions are not found when I expect them too be. The package is installed and it even works for the CT runner, but not for e2e runner. If it matters, this would also happen in our old Cypress 6.8 setup as well. Does the fact that it works for CT but not e2e indicate something obvious? Maybe the way we file preprocess is not playing nice with the library..? I really have no idea, this one really confuses me. @User you don't need to answer this, but I figure you might have the most context.

Hello, I have an issue with Github Actions, when I run my tests into two containers, I only run them for chrome but for some reasons

electron: headless

is runned too. But all of my containers passed. And those didn't finishes for some reasons so the Cypress Dashboard is running forever. EDIT: Looks like I'm not alone https://github.com/cypress-io/cypress/issues/16142

The

findByRole

error points out directly to testing library not being setup

I would suggest you check the support file for e2e (if it was not customized,

cypress/support/index.js

) where there should be the following import line:

js
import "@testing-library/cypress/add-commands"

huh, I thought that was supposed to be done in the support/commands.js file, as they suggest? you mean doing like this on the right though?

No, you are right it is supposed to be done in support/commands

you should see that commmands is actually imported by support/index.js

no need to install it in plugins

What I suspect is that the supportFile flag in cypress.json is pointing to another file

hmm, this is my config now

can you show your support/index.js file ?

or check that it imports the commands

and if it does... well console.log in the commands file

to explain something else in more detail. The old way of running component tests, I would see my e2e tests listed along with my CTs, but I would still be able to run my E2E tests with testing library. So it seems there is something friendly between the CT setup and the testing library. And here is that

you should have 2 support files

because the css imports are not very useful for e2e

and could make them slow, but most importantly break them

ok, just the same idea for the pluginsFile?

exact

Ok, I have this now, which I'm sure will be better long term or for other things, but still not resolving this testing library issue 😦

can you console.log('commands') at the top of the commands file and see if it appears in the console of the browser running the e2e tests

Or I just noticed this, which doesn't look right...?

this is a visual mistake but should not be any difference at runtime

Nice catch for the visual mistake.

I wish we had a GH issues integration in this discord

... sure would make creating issues way better

We can build it in our free time 😂

I wouldn’t fix this because Adam is about to rewrite

Did you mean this exactly, for the console? I don't see any console in the browser with this

just this