I want to choose which url to run tests on by telling it in the cmd. I have two urls under cypress.config.js file env: {live: "x" and staging: "y"}. So idea is if i CYPRESS_RUN_ENV=live in the cmd, then baseUrl is overwritten to be x. How would i do this?

We are on Cypress 12.8.1 and were having no issues until a few days ago. The UI of Cypress would stop responding on our Windows development laptops and our AWS test box has followed a day later. No updates, version changes, config changes, code changes or anything happened; the crashing across the board is seemingly random. Help.

We've seen these errors pop up here and there, but when we fix them, there's no way to make sure they don't regress in the future. Is there a way to write component tests for components which render on the server and client to make sure new hydration errors aren't introduced?

The application follows two factor authentication. It first navigated to application login then when we click on login it takes us to Microsoft login and then redirects back to the application. I am trying to execute two test case files(.js) one after the other. I am doing so by importing them into a spec file and running it. The first step in both files is to login and then perform some task in before each. Each file has different user credentials to login to. The first file with the first user, logs in and executes cases, but when the second file needs a different user login with his credentials, an error is thrown. I am calling a common login function for both files and only modifying the "user" parameter. Can someone help me with a solution? I have mentioned the login function I have used.                        Cypress.Commands.add("login", (user) => { cy.sqlServer(select USERID, password from table name where User=${user}).then(function (result) { var userID = result[0] var password = result[1] const credentials = { userID, password } cy.session([userID, password], () => { cy.viewport('macbook-16') cy.visit('https://applicationurl1.com/') cy.get('.login-btn').click() //clicking accept cookie button cy.get('#onetrust-accept-btn-handler').should('be.visible').click() //clicking microsoft login button cy.get('#microsoft-external-auth-button').should('be.visible').click() //redirected to microsoft login cy.origin('https://login.microsoftonline.com/', { args: credentials }, ({ userID, password }) => { //entering username //clicking next //entering password //clicking 'login' button cy.wait(1000) }) }) })})

Hi, is there a way to run cypress tests against the branch of the repo being pushed to git, without running locally? I'd like to be able to test the code in a push or pr, without a "live" app. Thanks in advance.

Example: I have a before call that gets a user in a specific state, if the test fails during this portion for whatever reason and then reruns it will always fail on the second run due to that state that its in now. I would like to do some kind of check that if a rerun is happening skip the before call.

Exactly as the title says I am curious if and how it is possible to edit the generated script by adding a new spec in Cypress studio. If this is possible that would be very usefull.

Is there a newer version of Chrome than v107 available in docker images? https://github.com/cypress-io/cypress-docker-images/tree/master/browsers I believe we're encountering a bug in our app that only shows on this version and would like to run my tests against a newer version to see if my theory is correct. I was expecting to see some updated versions since Chrome is on v112 now and these docker images don't seem to have been updated for 6 months+ Thanks

Errors for Below codedescribe('ITUS Test', () => { beforeEach(() => { cy.visit('https://buat.itus.co.in/homepage', { pageLoadTimeout: 240000, onBeforeLoad: (win) => { // disable service worker win.navigator.serviceWorker.getRegistrations().then((registrations) => { for (const registration of registrations) { registration.unregister(); } }); }, }); });

// test file describe('ITUS Test', () => { beforeEach(() => { cy.visit('https://buat.itus.co.in/homepage', { pageLoadTimeout: 240000, onBeforeLoad: (win) => { // disable service worker win.navigator.serviceWorker.getRegistrations().then((registrations) => { for (const registration of registrations) { registration.unregister(); } }); }, }); }); it('should display login page', () => { cy.wait(5000); cy.get('#login-form').should('be.visible').retry({ delay: 1000, // time to wait between retries, in milliseconds maxAttempts: 5, // maximum number of times to retry the assertion }); const employeenumber = 'QA'; const pwd ='Itus@2022'; }); });

Anyone sene this an dhow the hell do I stop it: https://www.loom.com/share/66faf50834e642f891a18b49412284c0

Is there something like Intellisense for Cypress.env() available? When writing

Cypress.env(

I want to get a code suggestion for the available env variables defined in my cypress.config.ts. I just wanted to ask here before implementing it myself, since I'm annoyed to always have to look up my cypress.config.ts for my defined env variables 😄

What is cypress cloud? Is it a CI tool? Where do your tests run when you run them with cypress cloud? I was under the assumption that it runs on a VM using cypress cloud.

Reading through the best practices document, under Selecting Elements (https://docs.cypress.io/guides/references/best-practices#Selecting-Elements), the best practice for Cypress states to use a

data-*

attribute to avoid brittle selectors that are subject to change. They also state that they strongly endorse the Testing Library ethos and approach to writing tests and strongly endorse their best practice (https://docs.cypress.io/guides/references/best-practices#Selecting-Elements). However, the testing library prioritizes

data-*

attributes as the lowest method selection (https://testing-library.com/docs/queries/about/#priority). Personally, I agree with the testing library's approach and guiding principles, but this section on Cypress's best practices guide felt very contradictory to me and am curious if I'm misunderstanding anything.

In the past 24 hours all my suite runs limit the specs displayed in the UI to 30, even though it knows I ran more, and the overview shows the correct summary, but I cannot see more than 30 of the specs that ran. I've opened a support ticket, and support has responded they are looking at, but it has been nothing but radio silence and there are no updates on the Cypress dashboard indicating this "visual" issue. In addition, it appears video uploads past the 30 cap fail to upload--which leads me to believe that maybe it isn't a fully visual issue. Please help.

Goodnight! Has anyone encountered the error below when running Cypress on Jenkins, on a Linux machine? ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

Hello guys Im having a problem with Github Actions and I dont know how to solve it some expert willing to help me? 😦

We are currently not running tests in parallel. Any pointers on that

I've enabled retries by passing in the retries object in my cypress.config.json

"retries" : {
    "runMode": 1,
    "openMode": 0
  }

My full command was `npx cypress run --spec My terminal never displays the second attempt. When running it in openMode, it does show the second attempt.

I am having issues with my i18n. I don't want to import it to cypress but i would rather fake the response of the $t fucntion but i am clueless how to do this and cannot find anything about it. Can someone send me in the right direction?

Hi, I am trying to perform some e2e tests. I have to access a web application, and it redirects me to the okta login, I type user and password and click on the login button. When I do this it should redirect me again to my web application, but it does not. What it does is to return to the okta login. This does not happen manually, and using selenium either. How can I fix it? Thanks

For e2e test?

Has there been any updates on Cypress being able to interact with chrome extensions? The team Im working on is using dApps and it would be really beneficial for us to be able to use our wallet extension during tests.

There are other forum channels, I think a dedicated group general chat is better. Turning this into a forum has killed that chat, you could just use Reddit at that point

For context, I have to pass a header to all outgoing requests to get past authentication and bot protection, so all requests are now shown as intercepted. This results in every request showing an interception and can make finding aliases I'm interested in tedious. I'm not even sure if this is possible, I've been hunting through the docs but have been unable to find anything. I'm hoping someone else has solved this?

Current behavior Hi Team, When I am hitting window.appEventData in my application, without cypress it is showing three EDDL events just after website loads. And when I am running the same thing in cypress runner then it is only showing first EDDL event. I tried to debug and I found that all three EDDLs are loading when I am opening one new tab in cypress runner window. Unfortunately, I can not automate second tab of cypress window. It there any solution to this problem? Please refer below piece of code: cy.window().then(function (win) { //Validating "Page Load Started" attribute expect(win.appEventData[0].event).equal(event1) // Passing expect(win.appEventData[1].event).equal(event2) // Failing but passing in second tab of cypress runner I am using "cypress": "12.7.0", Also I did tried the same in lower versions as well but it was not working. Desired behavior If it is able to load all all EDDL events in second tabs then it should also loads EDDL events in first tab of cypress runner. Test code to reproduce cy.window().then(function (win) { //Validating "Page Load Started" attribute expect(win.appEventData[0].event).equal(event1) // Passing expect(win.appEventData[1].event).equal(event2) // Failing but passing in second tab of cypress runner Cypress Version 12.7.0 Node version 10.24.0 Operating System Red Hat Enterprise Linux 8.6

How to send mail and receive mail by using cypress

Hi, do we have any statistics on individual browsers. Speed of cypress loading itself, speed of test processing, etc. Did anyone do such a survey?

I'm a Quality Engineering Tech Lead and the company I work for is going to be looking for some Cypress Quality Engineer's later this year. I just wanted to check if it's acceptable to do a post like this in the future to look for candidates? If it's against the server rules I understand, just wanted to confirm since I didn't see anything in the guidelines. Thanks!