!duplicate

Uh oh, It looks like you have posted the same question in multiple channels. Help us prevent spam by removing any duplicates of your questions, Thanks! 😀

Cypress 12.0.2 breaks (for me) on the following:

cy.get('button').contains('Save').click()

The error is:

CypressError: `cy.click()` can only be called on a single element. Your subject contained 2 elements. Pass `{ multiple: true }` if you want to serially click each element.

It works if I change it to:

cy.contains('button','Save').click()

There is only one Save button on the page and I've seen this in testing two different apps. The original version works in 12.0.1

What do you see when you click on the two elements in the test runner? The two yielded elements should be printed to console and see if there is any hidden element

Interesting, there is a second button present. The 'other' button is in a modal... not visible. When I query specifically for it,

get

fails. This is definitely different behaviour in 12.0.2.

Hello all, since this morning I've been having issues launching on my local machine (MacOS) . It was working fine for the past 6 months. We are currently running on Cypress v10.10.0 (however I have tried updating Cypress to the latest version and it didn't help). I have tried installing and older versions of Edge (last update was on 8th Dec) and also completely uninstalling Edge using AppCleaner and installing Edge Beta (seen in screenshot). We are using edge for testing some marketing trackers which don't work in Chrome in cypress by default. Testing headlessly works but launching using --watch or --headed with --browser edge (or edge:beta) it either is unable to connect as on the first screenshot or it returns this error. ---- read ECONNRESET Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) The Test Runner unexpectedly exited via a exit event with signal SIGABRT Please search Cypress documentation for possible solutions: ---- I have also tried going to File -> View App Data and deleting the project folder

I don't know if this is your problem, but I have seen Cypress get weird if the browser is set to auto-update and the update has downloaded, but not installed

Hey, thanks for the reply. Unfortunately that's not it, because when I downloaded an older version I automatically disabled auto-updates

Hello everyone, I’ve just upgraded Cypress to

12.1.0

(from

9.6.1

) and now I’m getting the error

Cannot overwite the contains query. Queries cannot be overwritten

Any idea how to fix it?

comment on https://github.com/cypress-io/cypress/issues/25078 asking for it

It seems that I didn't go far enough back when installing previous versions , I have installed the Edge-104.0.1293.54 (a version from June) and it seems to be working now. I have disabled auto updates.

A bit related to https://discord.com/channels/755913899261296641/755921440359841852/1052874337973186580 Since the upgrade to Cypress 12, the

click({multiple: true})

doesn't seems to work: If we do:

typescript
// before Cypress 12, this line was closing all notifications
cy.getNotificationsQuery().click({ multiple: true });

we got the error:

console
We initially found matching element(s), but while waiting for them to become actionable, they disappeared from the page. Common situations why this happens:
- Your JS framework re-rendered asynchronously
- Your app code reacted to an event firing and removed the element

You can typically solve this by breaking up a chain. For example, rewrite:

> cy.get('button').click().click()

to

> cy.get('button').as('btn').click()
> cy.get('@btn').click()Learn more

indeed, the click will remove one element and the second click complain. So we modified the code to have:

typescript
    cy.getNotificationsQuery().as('notifs').click();
    cy.get('@notifs').click()

we got the error:

console
cy.click() can only be called on a single element. Your subject contained 2 elements. Pass { multiple: true } if you want to serially click each element.Learn more

Endless story 😄

A bit related to httpsdiscord

Would be great to have "Cancel run on test failure" per

--group

Since one group on a CI job can cancel another one, it reduces the value of "Rerun workflow from failed"

Have you submitted a request for this? - https://github.com/cypress-io/cypress/issues/new?assignees=&labels=&template=3-feature.yml

Will do, thanks!

not just group, you could add all the filtering; tags, etc. for instance cancel normal runs on failure, but don't cancel cron jobs so we can get a full perspective

I don't have enough evidence to open up a Github issue yet, but in addition to a previous issues I've mentioned, Cypress 12.2 (I gave it another try after the .2 bump) gives me "maximum call stack size" errors in several places. I don't have a reproducible example yet but it's something to keep an eye out for. Downgrading to 11 makes the errors disappear.

Since I haven't seen anyone mention the error yet my suspicion is that it happens more frequently in certain areas of complexity. That's going to make a reproducible example tougher to provide for sure.

Hello everyone, is it possible to select elements by their ``data-*`` attribute in Cypress Studio? Cypress Studio seems to prefer IDs over class, but I think it would be smart if it preferred for example ``data-qa`` attributes if present

Hello everyone is it possible to select

Hi everyone, it looks like there is a bug with cypress regarding selecting elements with case-insensitive selectors, this is a valid css selector

It even works in the Cypress Runner

This is v11.2 and we cannot upgrade at the moment

Really liking the update to "Overview" in cypress cloud!

The mobile view on my iPhone 14 is really broken of the dashboard, it seems like the Cypress team has put some work into making it responsive, but when I start navigating between tests and suites it becomes really broken. Is there any consideration in the future to make the dashboard fully responsive ?

Hey @powerful-orange-86819 , great question! Mobile usability is an ongoing conversation amongst the members of the design/product team. I don't have any hard dates, but iterations will continue to be made. Would you mind submitting an issue regarding this question as well? We would like to document the amount of users that would find value in full responsiveness - https://github.com/cypress-io/cypress/issues/new/choose

I'm getting this error

Any help?