Hello everyone, I'll ask this here because it's not a really technical question: I'm approaching Cypress but I'd like to know if there's some sort of implemented way to make someone who is not a javascript coder, run Cypress tests Say I want a tester to enter text inputs and proceed with for example, filling registration forms and browsing pages Would a GUI dashboard built on Cypress be the only way?

You could use the Cypress Studio for a GUI led way to write tests, though I'd still recommend having someone with JS knowledge around for when the tests are flaky and you need to make tweaks https://docs.cypress.io/guides/references/cypress-studio

Thanks, I'll check it out!

@best-flower-17510 any update on the issue no 4886 https://github.com/cypress-io/cypress/issues/4886 I found that some one tagged it as stage proposal and type feature and it's extremely painful when running in TDD approach as you know cypress is independent of all specs so, we wish to run only failed test cases (but not retries) please can you help us know if anything is being worked out on this useful proposal of rerun only failed tests or retry test failures

Anyone had trouble with aliases losing their value? I have a complex test that started doing this after upgrading to v12. I can't reproduce it in a simple test yet though.

With nothing but a

cy.visit()

in between, the Yield disappears completely.

This is definitely a Cypress 12 issue; rolling back to 11.1 fixes it. I just wish I knew how to reproduce it more generically.

@astonishing-city-18705 any update on the below issue which is open for 3 years how to deal with the situation https://github.com/cypress-io/cypress/issues/4886 The use case is: I change some code and then run the tests using the Test Runner UI. Running them takes 10 minutes and 3 tests fail. For the next several minutes I'll focus on these 3 tests, changing code and rerunning them many times. While I do this, I want the Test Runner UI to only watch/rerun these 3 tests, until they pass. When I'm done fixing the issue, I can rerun the whole batch before I commit and push. So this request is really for an improved developer experience while investigating issues, not as a solution to handle flaky tests. @everyone what's your opinion on this feature and do you think its useful to you

> Please be patient, only post your question once in 1 channel and do not mention/ping members unless they are already in a conversation with you. From #763097415896268840 . If you have a Cypress Cloud subscription, you could reach out to Cypress support to escalate. Pinging Cypress employees on here (and then tagging everyone) is just noisy As for asking if it's a feature that would be useful, not really. I'd see it more as a 'nice to have' rather than a feature that would drastically improve my experience

Hello everyone! 😀 it is worth upgrading from Cypress 9.7? Which version should we upgrade to? Is upgrading to 12 risky? Are there any major improvements?

(performance wise)

We are using cypress to do integration testing for our react app

well, i don't think it is terribly useful, but one could implement it on top of cypress-grep plugin

The recommended best practice is to use

it.only

when pinpoint working on fixing specific tests. I don't find any issue with doing it this way personally.

Cypress 11.2 is plenty stable for me. I can't use Cypress 12 yet (see above) because I'm mysteriously losing the value on some of the (many) aliases I'm maintaining during my tests. It's easy to downgrade versions if it doesn't work out, so I'd say just get the latest and give it a shot.

There are quite significant changes between cy v9.x and v10.x though. And the automatic migration didn't work at all for my project so I had to go through the changelog and make changes manually. It wasn't too much effort, but something to be aware of if still on v9.x

Not sure where to post this question. Since I added cypress to my Angular project, In vs code, my intellisense marks all of my Jasmine syntax as incorrect. I am currently using Angular version 14 and Cypress 12.01

might wnat to put this in #763105090679865354

I'm still trying to grasp the retrying/querying changes in Cypress 12. Consider this code

cy.get('table tr')
  .eq(2)
  .find('a')
  .should(/* assert its href */)

If the last assertion fails, will it retry the full chain from the top? Now, make it a bit more complicated. Add another assertion in the middle:

cy.get('table tr')
  .should("have.length.gt.5") // <---- intermediate assertion
  .eq(2)
  .find('a')
  .should(/* assert its href */)

If the final assertion fails, what will be retried? The whole chain, including the intermediate assertion? Or just the the

.eq(2).find('a')

part? Thanks!

yes, read https://glebbahmutov.com/blog/cypress-v12/ and what you found is a bug https://github.com/cypress-io/cypress/issues/25134

Thanks! The blog post is super clear and helpful. Hope docs.cypress.io could incorporate some of those examples for better visibility :).

I would read the https://on.cypress.io/retry-ability guide, it has been updated

Thanks. Does the same concept apply to built-in assertions? Meaning

cy.get('tr').find('a')

will retry the whole chain until

a

is found?

These are not assertions, these are query commands (and they have built-in existence assertions too). See which commands are queries at https://docs.cypress.io/api/table-of-contents

Yes, they are queries, that have built-in assertions. And I'm wondering whether failed built-in assertion only retry the query they are related to, or the whole chain

thanks will move

the entire chain (of queries)

Can we test Microsoft WCF Services using Cypress ? WCF Services are hosted with various endpoints like BasicHttpBinding, NetTCP, NetMSMQ et. - https://www.c-sharpcorner.com/UploadFile/0c1bb2/endpoints-in-wcf/

I have a problem that in one way or another keeps coming back. I use Vue 3 and because of vue reactivity the DOM changes every time I press a button on a list. I need to press all the buttons on that list, so my question is, what would be the pseudo code for such solution?

is there a cypress playground that I can use to create an example of the problem?