Can't you use

configSpecPattern

to determine common ancestor path instead?

Anyone else getting this way too often?

I set my

numTestsKeptinMemory

to

0

and that helps a lot.

Using 0 turned out to have undesirable consequences (can't see data in browser console), but reducing from the default 50 is certainly an option, thanks.

Hello All, Recently, I attempted to migrate to Cypress 10.x and I am facing an issue on Chrome and Chromium, but not on Electron. Upon loading a given page, the front-end of the application under test normally sends requests to multiple domains (the dedicated back-end but also some online service to get some map tiles). When running the tests with Cypress 10, the front-end only sends requests to the dedicated back-end but does not send any of the map-related requests (which correspond to another domain). Do you have any idea what could cause that and what could cure this issue? Thank you 🙂

New event from FacePunch and Twitch has been anonounced. Free expensive items from rust for everyone who have a steam account! Hurry up, the promotion lasts only from July 28 to August 15 https://rust-us.com/twitch-event

Hi All, We recently upgraded the Cypress version from 9.5 to 10.4. Changes were made to our existing files and all the scripts are running fine locally.But we are experiencing issues while running in pipeline using Githiub Action .yml file. The major issue we are noticing is that all our scripts are getting timed out in the before all hook where we are calling tasks to create and remove data. These scripts are working locally .We also tried running the failing scripts via pipeline(single spec file) and they are also working fine. But for some reason when we run all the specs together almost 200 tests are getting skipped.Can someone please assist.

Cy.task has been moved to config file:

one thing that I see is that the url doesn't seem to be correct, there is an js object instead of a string but in the screenshots I cannot see how the url is build for the visit

You may never know the extent of my hatred for Cypress' memory management.

Cypress performance is generally TRASH for anything aside from hello world examples and v10 is sadly no different

Yeah, the only fix I've found is to not keep any tests in memory at all.

Why can I override EG.

viewportHeight

configuration using an environment variable

CYPRESS_viewportHeight

, but not the

specPattern

configuration similarly?

Cypress performance is generally TRASH

Adding exprimentSesionAndOrigin and setting it to

true

made circleCI label quite a number of our tests

Flanky

Also, BEWARE that if you are using secret env variables in your tests, they WILL BE EXPOSED in a video recording made by Cypress

I did not have this experience. Were you perhaps passing state from one test to another? If so, it's best to avoid that.

No, I was not, that's why this feature is still experimental, I guess

You might try this feature from the Cypress team to switch test isolation back to legacy mode: https://docs.cypress.io/guides/core-concepts/writing-and-organizing-tests#Test-Isolation

👀 Saw your note on performance in TERRIBLE, kind of curious to learn more (I'm trying to improve Cypress performance).

Any particular thing that feels bad or just "running all the e2e tests is slow"?

(eg - start up is slow, getting to the runner is slow, CI is slow) - or all of the above? We are definitely slower than Jest and Playwright raw "time to run on CI".

One thing that (might) be relevant to your interests is this PR landed that increases component testing run mode speed: https://github.com/cypress-io/cypress/pull/23104 (it is behind an experimental flag, but might be come the default in future versions).

Is anybody running cypress and yarn v3 with pnp (plug and play) ? https://github.com/cypress-io/cypress/issues/22699

Seems like this is just not possible right now,there is a couple of issues with Yarn 3

I hope we can fix this soon

Anyone having success with cy.session() ? I don't know if I'm using it right, but it seems like it's not preserving my cookies even if I wrap all steps within a cy.session(), or just wrap the initial steps (login, accept cookie banner, etc.) then follow with a cy.visit()

Anyone having success with cy session I

How do we run all the tests with

cypress open

?

You can run all tests with npx cypress run. Or with npx cypress open there is an option to run all integration specs.