I'm testing if my users can login:

typescript
cy.el('inputEmailAddress').type(Cypress.env('CUSTOM_EMAIL'));
cy.el('inputPassword').type(Cypress.env('CUSTOM_PASSWORD'));
cy.el('buttonLogin').click();

locally this is fine, but on my CI sometimes the second field isn't filled in. Adding some waits seems to fix it:

typescript
cy.el('inputEmailAddress').type(Cypress.env('CUSTOM_EMAIL'));
cy.wait(500);
cy.el('inputPassword').type(Cypress.env('CUSTOM_PASSWORD'));
cy.wait(500);
cy.el('buttonLogin').click();

has anyone else experience this issue with typing multiple inputs in a row?

@gray-kilobyte-89541 Hello I am trying to connect MongoDB with cypress for delete some data. Please help me how can I do

Have you read his blog?https://glebbahmutov.com/blog/testing-mongo-with-cypress/

I try this but unable to connect may be small error but unable to find. I am new.

I have added a new lesson "Lesson g1: Visit every page using the links found on the page" to my course https://cypress.tips/courses/cypress-plugins and just for you I made it free 🙂

Thanks

Hi here, Is there a way to point a custom e2e.js file e.g.

customeE2E.js

under` /support` folder? for cypress run

Hello everybody, I am looking to run Cypress tests through GitHub actions on multiple browsers. For whatever reason, tests on Edge, Webkit, and Chrome using cy.request() timeout and fail when trying to access our server. Tests on Electron and Firefox are successful. It is worth noting that all these tests pass when run locally on the Cypress web app. Would anyone be able to provide insight on what may be causing this issue? Thank you in advance

"cypress run --e2e --config supportFile=cypress/support/customE2E.js"

you can always change the support file location for e2e if needed https://docs.cypress.io/guides/references/configuration#e2e

Hey, I am starting to introduce Cypress to our company and am writing the first e2e tests right now. We are using a CookieBanner from CodeCentric which I would like to disable programatically. Working with

cypress open

and having an actual browser where the test runs the following code is working:

ts
beforeEach(() => {
    Cypress.on("window:before:load", (window) => {
    window.localStorage.setItem("some_key", "some_value")
    window.localStorage.setItem("another_key", "another_value");
  })
})

But running this with

cypress run --headless --browser electron

does not work and it seems like that the items are not set inside

localStorage

. I tried to check it with

ts
expect(localStorage.getItem("some_key")).to.not.be.null;
expect(localStorage.getItem("another_key")).to.not.be.null;

Is there a way to set some

localStorage

items in the headless mode to get rid of my cookie banner?

I think you might be overcomplicating things with the

window:before:load

. Have you tried doing a

cy.setCookie()

in your

beforeEach()

before your

visit()

command?

No, did not try it yet. Unfortunately they are not checking cookies but some entries in the localStorage.

So unfortunately this does not help me 😦

And if you try it a bit different so not using window before load but using cypress window

js
cy.window().then((win) => {
  win.localStorage.setItem("some_key", "some_value")
  win.localStorage.setItem("another_key", "another_value");
})

If that doesnt work, there is a plug called localstorage commands. Never used it before but it might help.

anyone experience a dropdown that can't be clicked headlessly with electron, but can be clicked just fine headed? racking my brain trying to find a workaround

How do you click in your dropdown. Are you using cy.select()?

Or is it not a real dropdown?

it's one of those "fake" dropdowns that uses

cdk-overlay-container

Headed it works fine, but headlessly it fails to click as the dropdown elements are detached from DOM

Each of the

span

elements is the desired element to click.

Javascript
cy.get('span').contains('WF+ AVOD').click()

Did not know about this method. It kinda helped... unfortunately the cookie banner appears on the next page again. Will just disable it on the testing instance. Thanks for your help

Cypress

complains that the

span

element is detached from DOM at or before the

.contains()

but only when running headlessly

@mysterious-belgium-25713 do you have any ideas? 🙂

will it give a different result if you would do

js
cy.contains(".mat-option-text","WF+ AVOD").click()

just tried that, still

detached from DOM

only headlessly, works fine headed (Electron 106) for both

i also checked, there's no network calls being made when I click to open the dropdown, so there's nothing to wait/ guard

And what if you would try to do headless with chrome and see if that yields a different result

npx cypress run --browser chrome

? or do I need to specify the path to the chrome binary?

just like that