hey man, did you figure it out?

My test was stuck in the middle of running test. No errors is shown but keep on loading. The same test runs perfectly in the previous/old version. @billions-barista-30103 team need to look into it .

Hi, I noticed that when cypress is in open mode, when I add new or remove spec file, this change is not reflected in cypress! I have to restart cypress to see the new specs or the removed one actually removed

I made a bug for this all ready: https://github.com/cypress-io/cypress/issues/22303

I guess there is a bug with the vite devserver

const viteDevServer = await createDevServer(startDevServerArgs)

transpiles into something like

ts

wrong

I doesn't seem to have the correct version of the dev server

what is the correct vite devserver version for cypress 10?

copy this to vue comp test channel

Is anyone else seeing their run times drastically increase when running the tests in electron in Cypress 10? The good news is that the tests run almost as quickly in chrome in Cypress 10 as they did in electron in Cypress 8. But here's a few benchmarks I took just now from our Github Actions pipeline Test1 Cypress 8 electron - 17s Cypress 8 chrome - 27s Cypress 10 electron - 47s Cypress 10 chrome - 21s Test 2 Cypress 8 electron - 12s Cypress 8 chrome - 19s Cypress 10 electron - 30s Cypress 10 chrome - 13s Test 3 Cypress 8 electron - 19s Cypress 8 chrome - 22s Cypress 10 electron - 39s Cypress 10 chrome - 16s For some bare minimum context, we have a Vue 2 frontend, Node backend. We're running our tests on virtual Linux runners on Github actions using Node 16.15.0 So if this is a bigger issue, I can get more info and submit an issue somewhere. I'm not worried since I can just flip our pipeline to use chrome. But this was really weird to me and just wanted a gut check on whether this is happening to anyone else? Or is it just our app?

vite is not restricted to vue

This is really useful information for the Cypress team. They've been looking at ways to improve performance, as well as investigating if there's been any degradation in recent versions. Is it only with Electron? Usually Chrome is the hungrier of the two in my experience cc @adventurous-dream-20049

you trapped into the

.md

trap with this one 😄 the folder is actually

__tests__

I only tried the differences between chrome and electron, since those were the two browsers I was already using for different tests But yeah, I found it really weird at first, too, because we were using electron for everything it could handle since it was noticeably faster. But then I did the version bump on Cypress and all the tests were taking almost three times as long to finish

Argument of type “login” is not assignable to parameter of type ‘keyof Chainable

I have file cypress.d.ts and there i declare namespace Cypress { interface Chainable { login(): void;} }

You can find the custom command guide for typescript here: https://docs.cypress.io/guides/tooling/typescript-support#Types-for-Custom-Commands It doesn't involve creating a cypress.d.ts file

Anyone running cypress 10.0.3 or 10.1.0 on CI (jenkins for me) have issues running tests on Electron and firefox? Get the “Still waiting to connect to Firefox” message Want to know if this is a regression in 10. Works perfectly fine for <10

Gitpod with Cypress 10

@rapid-yak-87393 what are the dev servers that should work with cypress 10?

Thanks for flagging this! Sorry I'm just seeing it @fresh-doctor-14925 @high-shampoo-86680 can you send me a PM? I'll respond as soon as I'm back next week.

Hi, I previously used the Cypress watch and reload plugin (https://github.com/bahmutov/cypress-watch-and-reload) to automatically have tests rerun if I make code changes. However, that plugin does not seem to work with Cypress 10 (or at least I was not able to get get it to work). Now I know this is a 3rd party plugin, but I was wondering if Cypress 10 maybe already supports rerunning tests when there are code changes? (Currently I keep having to click on the "rerun all tests" button every time.) - any tips or info would be appreciated!

Hi @limited-room-30929, you can find a list of our supported frameworks and devservers here: https://docs.cypress.io/guides/component-testing/component-framework-configuration

Hi everyone. I have a doubt in code coverage for cypress. i instrumented my application with nyc. I can see files under window.__coverage__ in the browser where my application is running and i can see undefined under window.__coverage__ in the Cypress automated browser when i run any test case.

I can see window.__coverage__ gives the list of files that are instrumented in the Cypress automated browser in the examples provided by cypress (screenshots)

those pesky 3rd party plugins, https://glebbahmutov.com/blog/cypress-v10-tips/#register-the-plugins