that doesn't seem to be enough

when I use @cypres/webpack-dev-server as custom devserver I end up with an error in cypress because it searches for a root element that is not there

it searches for

[data-cy-root]

but there is only

#__cy_root

and I have no idea why

is there a version dependency now between cypress 10 and @billions-barista-30103/webpack-dev-server ???

swap the #__cy_root id selector to become data-cy-root for component mounting (#20951) (0e7b555)

because this seems to have introduced a breaking change

if that is hard coded in cypress 10 that would explain it because I think I have a different dev server

Ok, I have updated the cypress-watch-and-reload plugin and made it work with Cypress v10+

Loved the migration wizard, Cypress team did great with it I tried it in this repo https://github.com/muratkeremozcan/react-hooks-in-action-with-cypress e2e worked out of the box I had component testing with cy 9 and cra, had to do a few manual steps for those followed the wizard changed all

mount

to

cy.mount

removed

@cypress/react

, and its imports from cy.js files removed

@cypress/react/plugins/react-scripts

import,

injectDevServer

from

plugins/index.js

applied all the knowledge here https://glebbahmutov.com/blog/cypress-v10-tips/ here's a sample migration PR https://github.com/muratkeremozcan/react-hooks-in-action-with-cypress/pull/148

Successfully migrated to 10x! Yay. However in the process the files didn't get renamed from spec.js to cy.js. How important is making this change and why change?

same for me, I'm keeping them e2e files spec, nothing has changed

things still work the same

Cypress 10 is great so far, but a few things require some mental retraining: - Memory leaks (in the site being tested maybe?) sometimes crash the runner. To mitigate this in previous versions I would close the runner after each debugging session, but now if you close the runner the spec list forgets which spec you were viewing. Remembering the spec filter with a cookie or something would fix this. - The spec list lost its collapse/expand all feature, as well as the button to clear the current filter. - The dark theme isn't my favorite... would be nice to be able to select a theme. I'm getting by with Stylebot for now. I dig being able to have screenshots attached to a log group. One day I hope to make use of component testing, if I ever test a React site.

if you ever apply @gray-kilobyte-89541 's solution to run-all https://glebbahmutov.com/blog/run-all-specs-cypress-v10/

find . -type f | grep cy.js

is your friend

I should upgrade find-cypress-specs tool

hmm, I love to overkill

Have you seen the new CLI tools that just released from TestRail? I'm hoping it will provide a native replacement for your

cypress-testrail-simple

plugin.

no, have not seen it

hello

can any one help nme

i have the problem, if install with npm i have a cypress.json and cypress.config.ts

that leads to an error

in ci and localy

What is the error?

Can you help with the error?

If you are talking about Gurock..!! If you are using Cypress for automation. Cy plugin is the best thing you have a single framework for everything.. Rest is money.

Hi all. Absolutely loving the new look cy10. Just a question about whether something is (if i've missed it) or could ever be a feature. I launch Cypress from within a wider CLI application, using the Module API. As such, I always start it in the testing mode and browser which I want making the initial Cypress window redundant (for this use case) now that all the specs are in the browser (which I love). I'm wondering if it's feasible (or could ever be feasible) to have that window headless, whilst keeping the browser visible?

The problem with this is that the window with the E2E/Component buttons is the slow-loading one. The browser is the fast-loading one. If you combined them you'd never be able to launch the browser quickly after it runs out of memory or whatever 🙂

I guess I wasn't suggesting that they were combined, just that I don't need to be able to see the E2E/Component window. Actually, if I think about it a bit more, I suppose the bit I don't need to see is the option to choose between e2e and component as this set of tests will only ever by e2e - but the browser section would still be useful. For a bit more context, we use Cypress with the excellent cucumber plugins to allow less technical users to be able to write integration tests against some of our applications - and the more buttons I can hide from them the better! It is of course a very specific use case and therefore probably not much use to the vast usership of Cypress, but I just thought I'd ask the question whether there was a way I was missing