i need help that how to avoid opening a new tab in cypress, just want to open the new link in the same window.

you can use this if the href has a - target=_blank att cy.get('').invoke('removeAttr', 'target').click()

M using cy.get("locator").invoke('removeAttr', 'target').click() @blue-bird-1589

helpp/........

Hi everyone! I'm having this exact same issue https://github.com/cypress-io/cypress/issues/9265 which was supposed to be fixed a while ago. In my case, it is running on Electron v94 with Cypress v9.5.3. Any ideas on what could be wrong? Thank you!

https://glebbahmutov.com/blog/cypress-second-tab/ and it is hard to say anything beyond this without seeing the app

try to repro what you're doing in this repo https://github.com/muratkeremozcan/angular-playground and work through the deltas

it may be because of the baseUrl mismatch try a regex matcher vs minify

perfect use case for cy.origin get 9.6.1

"experimentalSessionAndOrigin": true

in

cypress.json

try something like this command https://github.com/muratkeremozcan/auth0-cypress/blob/master/cypress/support/commands.js

Hello there 👋 I know that Cypress intentionally doesn't support child window access but I think I still have a valid use case and don't really know how to work around that limitation 😕 I have a Vue App that renders a component in a child window using this mechanism (https://stackoverflow.com/a/58534753) which is then basically "remote controlled" on the parent window. Of course I want to test its behavior but I don't know how if I cannot access the child window and its DOM. Does anyone have an idea?

Hi all, Has anyone else been seeing issues with executing the tests having runtime over 60 minutes timing out and the dashboard doesn't publish the execution report? We have been executing the tests locally and it passes however when publishing to cypress dashboard and triggering the entire suite together the tests timeout and details cannot be seen as the reports are not published. Could really use some help with this. Thanks

Hey, I have the following plugin file for cypress:

ts
export default ((on, config) => {
  // `on` is used to hook into various events Cypress emits
  // `config` is the resolved Cypress config
}) as Cypress.PluginConfig

I'm using typescript. When I run it on my machine it's working but when I use

cypress-io/github-action@v2

in my github actions I get the following error:

bash
Your pluginsFile is invalid: /home/runner/work/XX/XX/frontend/cypress/plugins/index.ts

It threw an error when required, check the stack trace below:

/home/runner/work/XX/XX/frontend/cypress/plugins/index.ts:14
export default ((on, config) => {
^^^^^^
SyntaxError: Unexpected token 'export'

My cypress config file is empty. What's the problem?

I'm having some problems with a flaky set of tests. Looking for some input in how best to deal with dropdowns where the options don't appear be loading fast enough. I thought I solved it by ensuring that the option was not disabled before selecting it.

it('should successfully submit a valid file', () => {
        cy.get('@evidenceIframe')
            .find(benEvidenceTypeDropdown)
            .find('[value="5"]')
            .should('not.be.disabled')
        cy.get('@evidenceIframe')
            .find(benEvidenceTypeDropdown)
            .select(5);

I'm new to cypress so please forgive me if this is poorly written

Thanks @gray-kilobyte-89541 but seems difficult to understand.

Hi everyone! I have an app at http://localhost which loads it's assets from a Vite devserver at http://localhost:3000 . Cypress is hitting the main app correctly, but it doesn't load the assets, leaving me with a blank page. Any ideias?

i want to kick off some VueJS component testing and i'm using ViteJS as a bundler. When I startup I do have a test file:

but when I start Cypress with open I get this dialog:

now this is not the default location but my

cypress.json

I believe is configured correctly:

json
{
  "downloadsFolder": "test/integration/downloads",
  "fixturesFolder": "test/fixtures",
  "commandsFolder": "test/integration/support",
  "integrationFolder": "test/integration",
  "screenshotsFolder": "test/integration/screenshots",
  "testFiles": "test/integration/**/*.test.{ts.tsx}",
  "pluginsFile": "test/integration/plugins/index.ts",
  "component": {
    "testFiles": "**/test/integration/**/*.test.{ts,jsx,tsx}",
    "componentFolder": "test/fixtures"
  },
}

and when I use the UI to add a test script it adds it to the

test/integration

directory but then doesn't see it 😦

I think that my problem may be that I'm using

npx cypress open

and not

npx cypress open-ct

(as I do want to do component testing atm) but doing that blows up with an error relating to my

vite.config.ts

file: > Cannot find module './comment_char.js'

btw, wondering is it only

open-ct

which will use ViteJS? or will

open

leverage that too?

I have sorted the Vite error above but I still get no test scripts listed

it's really looking like component testing isn't getting the love WRT to directory configuration

the UI always says it's looking for "spec" file even when the glob pattern is for

*.test.ts

not sure how literally to take it

but changing my test files to use the

*.spec.ts

convention makes no difference

@silly-dentist-68907 @adventurous-dream-20049 @lemon-oyster-64925 @cuddly-winter-72122 @wonderful-match-15836 @fancy-match-96032 can one of you help me get over this hurdle? if so I can provide you guys with a very helpful ViteJS plugin I created 4-5 months ago which automatically generates an interface definition for

Chainable<Subject>

on hot-module replacement ... meaning all of your custom commands are not only available at run time but automatically and fully typed (including JSDocs)

> for anyone using TS this is a really really nice to have

is this community used? I can see folks are online but an hour later I have no responses ... maybe I'm being too entitled but will have to abandon soon if I can't cross the start line

Thanks so much for reaching out with this great question! This may be best asked in #755921564108587038. Also, if you don't mind kindly refrain from using @ to reach out. It can get quite loud 😅 and we have several wonderful individuals that may chime in to help. I assure you someone with knowledge in the area will respond as soon as they are available.

we are heavy on TS, but there is absolutely not reason for config files to be TS. You don't have anything from prettier or eslint in TS for instance, they're all just for config. Try it in JS.