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?

you application has not loaded the javascript it needs before calling "popover" function?

so how can I fix this?

Oh sure, i have lots of images of the bugged out dashboard in mobile view, but they contain sensitive information, i'll have to censor some and create the issue

Yes, please sensor the sensitive information. Thanks for taking the time to submit this 😀

Feedback on Cypress 12: for us, the new broader retry functionality comes at a cost. In addition to aliases no longer holding a static value, when I chain an alias after a complex custom command I end up with "maximum call stack size exceeded" errors. The workaround for both issues seems to be to introduce another custom command,

.freeze()

, to precede the

.as()

. If there's a better way I'm all ears.

js
Cypress.Commands.add('freeze', { prevSubject: true }, (thing) => cy.wrap(thing))

Is this really necessary? I feel like triggering full-chain retries should be more of an opt-in thing. This makes the idea of storing values in a global object seem preferable to aliases. Yuck.

https://github.com/cypress-io/cypress/discussions/25437 Hi everyone! I've posted a discussion here. I'd appreciate any insights on this if you have come across this situation. Thanks!!

here's how I would approach it 1. implement progLogin, or the cy.session style of UI logging. Be using this everywhere other than (2) or (3). 2. atomically, explicitly test UI login in one test - do not repeat UI login anywhere else. With this you are 100% confident that UI login works 3. For UI logout, you have 2 options * UI login (as in (2)), UI logout - explicit, one atomic test. Do not intermix with other it blocks; 1 spec , 1 it block * progLogin or cy.session login (1) , then UI logout. Again, one atomic test.

Should Test Isolation clear all active web socket channels? I'm currently writing tests with sockjs library and when I open a channel, next test will still have those channels open and messages will be read by my ws command. I've made some workaround to clear the web socket channels in beforeEach, but i think it should come native with test isolation

Test isolation

Conmand retries