Matt Mitchell

Are there any workarounds to handle these dialogs if the iframes are from different origins?

I am also using the cypress-browser-permissions plugin, but it would be great if Cypress could support this without an additional plugin. It is not ideal especially when there are limitations...

Same here. I also use the in "open" view and it is including all .js files even though I see this in console: ``` cypress-grep: filtering using tag(s) "@webAppMonitor" cypress-grep:...

I double checked the plugin installation, and at least in my case it seems ok. Here my e2e.js Here is my cypress.config.js Here is output where it is finding all...

Here is the output: ``` cypress-grep cypress-grep plugin version 3.0.1 +0ms cypress-grep Cypress config env object: { ...grepTags: '@webAppMonitor', grepFilterSpecs: true, grepOmitFiltered: true } } +1ms cypress-grep: filtering using tag(s)...

It is like this: ``` cypress-test/ package.json config/ monitor/ subproject/ cypress.config.js cypress/ integration/ spec1.js spec2.js ```

@bahmutov specPattern is: `**/*.*`

> I think the problem comes when cypress-grep is setting the integrationFolder constant. if your cypress.config.js is not in the cypress folder then the plugin won't find your tests. >...

Nice catch @joshuajtward -- I think you meant to tag me though, as those were my screenshots. I have another config file that extends to the one I shared in...

Nice idea. In my case, I needed to do a deep merge between configs, so I ended up using lodash.merge for this. Here is a quick sample of a config...