Cypress 10 // Best time for UI testing (Get Started + Main Features)

[@LachlanMiller]

Glad you are finding Cypress CT useful! Thanks for all your content - I learned a ton from your TS handbook.

[@electrolyteorb]

You don't know how happy I am

[@hamadambyte6942]

Thank you Basarat

[@LachlanMiller]

I think you should be able to import the CSS in your supportFile, so it's available for all component tests (need to 100% verify this but it should work).

[@basarat]

Great suggestion I am sure that works

[@awaiskhalil2062]

Hi i try to run following command to run cypress ".\cypress open" but it is showing this error Cypress configuration Error Your project does not contain a default supportFile. We expect a file matching cypress\support\e2e.{js,jsx,ts,tsx} to exist. If a support file is not necessary for your project, set supportFile to false.

[@basarat]

The support file should be created for you if you run it on an empty project as done (and shown) in this tutorial. You can also copy it from the final code on GitHub if you want

[@awaiskhalil2062]

@@basarat i meant in latest cypress version 10.0.3 it is not importing support file auto. So if there is work around then please let me know. Thanks

[@191jassi]

Great Tutorial, Thanks 🙂, We have aurelia app, do you think cypress component testing will fly for aurelia app too?

[@basarat]

Thanks for the comment Will probably not get an official supported plugin from the Cypress team (my guess), but no technical limitation (that I can think of)

[@191jassi]

@@basarat Thanks for reply. Is there any documentation which I can refer to. I am new to unit component tests for aurelia

[@ankursehdev5448]

Great Tutorial! and Does this support multiple tabs and pop-ups now? Last I am aware I wasn't able to use this because of POP-UP sign in process I have in my application. What do you advice for handling pop ups?

[@basarat]

Thanks for the question most commonly the UI in the pop up tab is not written by us e.g PayPal or Google auth etc. So I would skip opening it by taking a backend approach to “action”, I.e. logging in the use by running custom headless sign in code in the test. This way I’m not testing third party code and tests run faster. A simpler option is to use a mock validator, but like all mocking, should be used carefully depending on what we want and what we don’t want tested in the real system. I know it sounds a bit difficult and real code would be great. I’ll try to make that demo someday

[@ankursehdev5448]

@@basarat It does make sense, I will try to use this now. Thanks for awesome content bro.

[@michalkotlicki4710]

Would it replace React Testing Library?

[@basarat]

Yes. Component tests are an alternative to RTL 🌹

[@somerandomchannel382]

@@basarat no its def. not.

[@basarat]

@@somerandomchannel382 engineering.udacity.com/cypress-is-superior-to-react-testing-library-heres-why-3fac0675910

[@vijaykoladara8302]

Please make a full course on cypress

[@basarat]

Thanks for the request 💯

[@gunasekarant6498]

@@basarat Yes please make both E2E & Component testing using React

[@arunyasekar9817]

where s the button coming from

[@basarat]

Thanks for the question Its coming from the button module imported at the top of the test

[@chrisdaman4179]

They will never be a real tool as long as they require a gui. We cannot get into the gui and all the docs are useless from a cli stand point. The gui does too much work for you.

[@basarat]

I think the docs cover the cli very nicely. The gui is just the icing on the cake