I thought I'd fixed this after reading about

element.trigger('click')

but it was a mistake. We're using storybook to display the page. I'm using the 'full screen' mode so it's not iframe related. Very simple test

cy.get('element').click()
cy.url().should('include', '/stores')

I've tried using

.wait(5000).click()

-

focus().click()

-

click({force:true})

and variations with `trigger('click')`too If I use the cypress ui - the test closes as soon as the click event is finished, it won't wait or anything, so I can't debug it. If I use the CLI in any way, the test hangs on the

click()

and doesn't do anything. If I use the

trigger('click')

the test runs but fails because the url doesn't change. Which makes me think the click isn't working there, either. Any ideas anyone? I've been trying this for a few hours now.

could you confirm Cypress version? If using 12 or over, I would be interested if this reproduces with something below 12, like 11.2.0? 12 introduced some changes with commands, it would be interested to know if the same crash happens before/after.

Yeah it's 12 - first time using cypress so it was a fresh install from a few weeks ago.

Possibly that router has some code to bust out of the iframe and take over window.top, which is where cypress is running. So this is an end to end test that visits a running instance of storybook to test a component, is that right? Have you considered writing component tests for this situation? Or is this already a component test?

Correct - we are doing component tests using mount with test-utils...the project used to require a java ui test because we used to use a nuxt app...but now we're making the components that another team are using. So storybook is the only ui and I wanted to get a bit of cypress experience 🙂