Hello guys, I have a problem with the new Cypress 10. On my project we use a security to reach the site, so if you want to reach a pop up with username and password shows but in cypress 9 I have manage to bypass the login on the site by given it in the url https://username:password@site.com but for some reasons in Cypress 10 is not working. Can anyone help me with these please?

What kinda error is occuring ?

**Vite + Cypress**: How to get them to work together? Vite included a change from using

process.env

to

import.meta.env

for all env variables - this is quite a problem because Cypress, when I run

cypress open/run

, is trying to transpile my Cypress code, which has imports of files using

import.meta.env

. It fails with webpack compilation errors. Has anyone resolved this issue for themselves? Note: this is specific to E2E tests not component testing.

You need to add basic authorization

auth

option to your

cy.visit

command https://on.cypress.io/visit

maybe do the

cy.wait('@responseForPageB')

before attempting to go to the tablist?

Hi Guyzz..I am facing this problem which I feel may be the issue on cypress side. I am mentioning steps that works on any browser except via cypress 1. Login to public website hosted by oracle 2. open hamburger menu 3. click console - Above steps should render page with multiple tiles. With cypress when setting chromeWebSecurity as false I see 404 API errors as shown in screenshot and if I remove this setting,the page loaded is empty due to CORS blocking. Can anyone explain what is the problem, if cypress is acting as proper browser then these api calls should go through fine? Appreciate, if anyone suggest some work around.

Hi guys, anybody tried using cucumber tags with cypress 10? do you have an example?

Hello I m experiencing something weird

Hey guys, my boss told me to try figure out why our cypress testing is failing but i have very little knowledge on cypress automation testing ( the only guy who knew about cypress left for a new company) here is the test that im trying to get back to work and here is the failing message that im seeing what ik is that this test was working for many weeks and just started failing 3days ago any input at all, no matter how small would help me alot, thanks in advance 🙏 🤞

We are looking at implementing our Cypress e2e tests into our Azure build pipeline but I'm having trouble finding anything on the subject online, does anyone here know where I can go to learn more about that?

The docs has a few basic examples for azure. I vaguely recall an ambassador using azure example during one of their talks. https://docs.cypress.io/guides/continuous-integration/ci-provider-examples#Azure-Pipelines

Hi guys, I am running a Jenkinsfile with a command "cypress run --record" on the Included docker image, but after that it will never output the start or fail, just output 4 warnings and thats it. does anybody know what could be wrong? Also in this really old thread people are still having those hang issues https://github.com/cypress-io/cypress/issues/4925

i have installed CICD with AWS code pipeline i am using " npx cypress run --record --browser electron --key XXXXXX-XXXX-XXXXX " to record & i have projectId in cypress.config.js but system giving me error:- Your Record Key d30f4...3ce5d is not valid with this projectId: d30f4320-2281-XXXX-ad73-XXXXXXXX but sytem showing me Key as project id ( same code working fine locally )

Thanks, it works

Thanks for the reply badeball, I'll check it.

i have installed CICD with AWS code pipeline i am using " npx cypress run --record --browser electron --key XXXXXX-XXXX-XXXXX " to record & i have projectId in cypress.config.js but system giving me error:- Your Record Key d30f4...3ce5d is not valid with this projectId: d30f4320-2281-XXXX-ad73-XXXXXXXX but sytem showing me Key as project id ( same code working fine locally ) https://on.cypress.io/dashboard/projects/d30f4320-2281-4683-XXXXX-XXXXXX in cypress io URL system showing me key instead of projectId

the system not showing project ID in dashboard URL but system showing key

Vite + Cypress: How to get them to work together? Vite included a change from using process.env to import.meta.env for all env variables - this is quite a problem because Cypress, when I run cypress open/run, is trying to transpile my Cypress code, which has imports of files using import.meta.env. It fails with webpack compilation errors. Has anyone resolved this issue for themselves? Note: this is specific to E2E tests not component testing.

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

AWS codeBuild showing me this error ( any solution ) [641:0809/020517.543670:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process. [641:0809/020517.546278:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

when I run cypress with record Id I am getting an error that " wrong project id " but instead of the project id system showing me my record key as project id.. screenshot attached. https://ibb.co/hVWGz8P

Cypress is not getting env variables from a docker container I have this in my test file:

cy.login({
              username: Cypress.env('CYPRESS_USERNAME'),
              password: Cypress.env('CYPRESS_PASSWORD'),
            })

docker-compose:

environment:
      <<: *x-environment
      CYPRESS_USERNAME: 
      CYPRESS_PASSWORD:

It passes locally in the Cypress app but when I run it on Circle CI in a container Cypress is not getting the values from the environment variables set in the project

I am not sure how it would get them locally, but in your spec you would NOT prefix the vars with

CYPRESS_

https://on.cypress.io/env

why is that?I am not seeing that in your docs

Also, I have removed the prefix but still Cypress is not getting env values from Docker container

Are you sure you are setting them in the Docker container

I'm seeing strange things in our Cypress parallel tests running under Buildkite. If something goes wrong a the first try, the next try... runs "without running" I upload two screenshots 1. the first run (Cypress finds the tests and run them) 2. the second run after the failure of the first run (Cypress finds the tests but does not run them) any idea? 🤔 am I missing anything stupid?

it has the same run ID I bet on BuildKite, so it thinks all specs are already done. Find another env variable to use as

--ci-build-id

Got it, thank you Gleb!!!!