ok, I successfully added testing playground inside of chrome used by cypress,,, but it seems it is not working nicely... it's like it cannot select browser inside but selecting cypress elements,,, which is besides the point

but I guess this is not cypress problem, but rather the testing playground tool problem

its like it cannot target elements inside iframes

I will raise the issue there I guess

👍

Great report yes

This is usually a tough cookie

I wonder if we could open the Application UnderTest in a popup for those kinds of needs

... food for thoughts

can you link the created issue here so that others can follow?

Hi! I am having some trouble with conflicting type identifiers for Cypress and JQuery. Have posted all the details in this [stackoverflow post](https://stackoverflow.com/questions/69291905/how-do-i-resolve-conflicting-type-identifiers-for-cypress-and-jquery). Some comments/solutions are highly appreciated. Have spent a lot of time trying to get this to work.

Nvm I figured it out. Posted the solution as the answer. If there's a better way to fix it would still appreciate some comments.

Is it possible to have the React Devtools in the Cypress environment

It is hard but @User has a tuto fir it

Hello! Has somebody faced the issue, when Cypress changes a visiting url by adding /__/#/tests/_ and redirects to Page not found?

Hello, does somebody know about a good tutorial on how to integrate Cypress with BrowserStack? Tks. Update: I found this: https://www.browserstack.com/docs/automate/cypress in your opinion is this the best ressource to use?

Hi @everyone, I would need to populate a mongo db before starting testing, all using cypress, would there be a way to do it?

I think Gleb had a blog post about it

Might come in handy

thank you so much

Hi all. Does anyone know an approach to dynamically test a website with multiple languages? I’ve set a cypress.env.json in my project with url values for the site In different languages. Is there a way I can use these environment vars to iteratively execute tests?

hey, i'm messing around with component testing and had a question about terminology. the official docs and the cypress.json object look to mix "integration" and "end to end/e2e" with the same meaning. Now that Cypress is introducing "component tests", i'm wondering what the team's perspective on those terms is. to me, the typical cypress test of "visit a url, test some user flow" would be an end to end test (or "acceptance test", or "application test"). The new option for component tests would be more of what I think of as an "integration test". am I misunderstanding these terms? Does the team just have a different interpretation than I do? Or is this a case where the language maybe wasn't nailed down early and is now more complicated by the introduction of a new type of testing

as an example - the cypress.json config has an

integrationFolder

key, pointing to where tests can be found, defaulting to

cypress/integration

now, with component testing, you can override settings for either the "normal" cypress tests or the new component tests by using the

e2e

and

component

keys. i.e.

{
  e2e: { integrationFolder: 'cypress/integration' }, // Aren't the component tests "integration" tests?
  component: { componentFolder: 'cypress/component-tests' }
}

Hi, is it possible to test native mobile apps for Android & IOS using Cypress with BrowerStack? Can somebody send me some ressources about this? According to their official docs, we can't... https://docs.cypress.io/faq/questions/general-questions-faq#Do-you-support-native-mobile-apps

@User Cypress can't and never will be able to test native mobile apps

But you might be interested in this https://www.cypress.io/blog/2020/07/08/end-to-end-testing-mobile-apps-with-ionic-and-cypress/