@hundreds-library-57018 , consider setting your tests to be triggered by CI. When you do this properly the Git information will flow into the test run, and you can see exactly which pull request triggered the test. This will infer not only the team, but also the person and the pull request, so you'll know exactly which changes cause failures.

We're already doing this, Let's imagine the following scenario: I push a test which is flaky, during PR it passes. Another contributor (from another team) eventually creates a PR and merges it, my test will fail under his/her commit on master, git information would tell that another person/team is responsible for the failure. What I was thinking (and I'm not sure if it's possible) to instead of attaching a tag to a run (which has more than one thousand tests running) attaching a tag to each test individually (or something similar). So it doesn't matter much who triggered the run, we focus instead of the tests.

> What I was thinking (and I'm not sure if it's possible) to instead of attaching a tag to a run (which has more than one thousand tests running) attaching a tag to each test individually (or something similar). So it doesn't matter much who triggered the run, we focus instead of the tests. Ah I see, so some sort of metadata giving a single person or group ownership of a test? I can't think of anything built-in to help with this. Hmmm.

Hello team , cypress10.2.0 is stable or not??

no docs about cypress 10 in what's new page

Hi @rough-monitor-85122

Need to send an email from Cypress, but it returns 'will not send email results'. configured the cypress-email-results plugins https://github.com/bahmutov/cypress-email-results, but email not triggered, needed support on this

DMing and pinging random people with roles is not a good way to get support. There is a #763097415896268840 channel that explains better ways. 🙂

It's nearly midnight and I'm on my way to bed.

https://github.com/cypress-io/cypress-docker-images/tree/master/browsers Anyone know why this repos hasn't been updated with new browser versions

My approach is creating custom commands that take optional properties, that also makes separating the code from tests more clear, leaving only actions and assertion in the spec/cy files and all the necessary dependencies and custom function in their respective .js files

watching Front-End Test Fest https://vshow.on24.com/vshow/Applitools/?regPageId=20976#home

I just migrated a cy 10 repo to React 18 from 17 https://github.com/muratkeremozcan/react-hooks-in-action-with-cypress/pull/154 no issues cy 9 had issues with React 18 ,

hello can any one help nme i have the problem, if install with npm i have a cypress.json and cypress.config.ts that leads to an error in ci and localy

anyone had this error before?

Hey everybody, I have a general question about testing UI without any backend. Would the best practice be to use the intercept method or is there a better way?

Yeah, that’s how I’ve done this. We have a frontend app that we used to have a lot of e2e tests, I used intercept to stub the backend responses. Eventual plan is to move most of the tests over to the component test runner

Help me on this

Your selector does not exist in the DOM. You can break it up into

.get()

+

.find()

to see which command fails.

How

Write

Explain

Well, a quick example:

// .parent > .child > .child-of-child
cy.get('.parent')
  .find('.child')
  .find('.child-of-child')

Hello all, where do you recommend is best to raise this issue? "GitHub Actions table formatting of Cypress data has become messed up" I already raised it in GitHub Community but got no response there https://github.community/t/github-actions-table-formatting-of-cypress-data-has-become-messed-up/257450 as this did not occur during a Cypress version change, I'm assuming it was a change to GH Actions itself.

When running npx Cypress open it is opening the default spec files instead of mine, how do I get it to show mine?

place your specs in the

cypress/e2e

folder. that'll do it

Tkuuu 🙏

It's still showing the default specs (which are not in my project) @fresh-doctor-14925

You sure you're running cypress from your project folder? Sounds like you're maybe in the wrong directory

Yep, I had 2 Cypress folders for some reason 😅