we have an error with cypress e2e runs on github actions it involves peer-dependency with npm packages everything (servers and e2e) works fine locally

We are experiencing some issues where tests timeout and do not finish, but it happens very intermittently. Running locally, things pass pretty much 100% of the time, but on CI things get flaky and there are random failures all the time. Eventually CI times out after 2 hours and the test never completes. Does anyone have any tips on how to troubleshoot what might be happening? Since it times out, we don't have any videos or screenshots that get uploaded, and locally everything works.

The run started, but never completed. This can happen when the run is canceled from CI or when Cypress crashes during running tests.
Check your Bitbucket #1414 logs for more information. Archive this run to remove it from the runs list and analytics.

hi, We are running our tests from azure pipeline and cypress dashboard, recently the test videos that's being upload to cypress dashboard are broken and laggly, does anyone familiar with this problem?

Thank you. The solution was helpfully.

Hello Everyone. I am using Cypress on Rails for automating the application. Browser is crashed and display this screen. when i can watch logs debug this issue? Any leads will be great!

Hi @fast-ocean-24805 ! I wish I could provide some specific support here but I do not have that information. You can post again here in this channel or utilize our other user resources. Thanks for your support of Cypress!

Who controls or is responsible for updating the SSL cert used by cypress?

has anyone found a way to resolve the Webpack Compilation Error? seem like it happens with any 'fs'

has anyone found a way to resolve the Webpack Compilation Error? seem like it happens with any 'fs'

Thread

I want to set a variable (for the URL to our back-end) , what's the best place to do that? It's not really an env variable, just more a global cypress variable

@happy-dinner-13480 do you think baseURL?

No, the

baseUrl

points to

localhost:4200

, the URL of the client 🙂 so I need another variable to point to the back-end

@happy-dinner-13480 so you mean endpoints? E. g. localhost:4200/something/something

No, currently I have the API_URL configured in my

cypress.env.json

file:

{
  "API_URL": "https://api-test.***.com"
}

but I would rather have it somewhere else, since it's not a secret. I use it like so:

cy.intercept({ method: 'POST', url: `${Cypress.env('API_URL')}/api/v1/user/login` }).as('login');

You could have it as an environment variable and map it to

Cypress.env

https://discord.com/channels/755913899261296641/763105090679865354/986198337873129493

found it:

e2e: {
        env: {
            API_URL: 'https://api-test.***.com',
        },
}

ah that's also cool 🙂

@happy-dinner-13480 Whats the diff between defining env in config file and in cypress.env.json

It should be called exactly the same way with Cypress.env

Hi Team! Has anyone got a professional testing plan template I could use?

i would consider the

cypress.env.json

file to hold secrets like usernames and passwords, which this value isnt 🙂

is it possible to override the

clearLocalStorage

command to not remove anything from localstorage?

Hi. Can anyone recommend some resources that provide a deeper explanation of how Cypress works under the hood? Technical details, high-level architecture, etc...

I'm trying to set up a github action to run some tests, but I get this error. Can someone explain what is going on here? --force or --legacy-peer-deps doesn't do anything

An issue with node-sass package dependencies. Ensure all your project packages are up to date, as it seems one package that has dependencies has a conflicting version. In summary, nothing to do with Cypress by the looks of it.

Hello

I have an exact case like the one in Cypress docs

However, it is not selecting the option I want