Cypress in 100 Seconds

[@leoaso6984]

Ah yes, automated UI testing. That thing I'm definitely absolutely positively going to start doing... one of these days.

[@ASDFG856]

I have never seen a comment I relate more with.

[@SpongeAndLeo]

I basically exclusively test network calls using cypress these days. Powerful framework.

[@daniel29009]

Meet converted pyramid, tapes server and unit size discovery.

[@attila2246]

So all your PR's get accepted with 0 unit tests?

[@leoaso6984]

@@attila2246 Me: Hey, I just created a new button component. Pls review. Me: OK, but you didn't add any unit tests. Me: uhhh yeah, but... when I opened the browser and clicked it, it did the thing. Me: ...........eh, good enough for me **merges PR**

[@negary666]

I don’t even do web development but these videos are just too entertaining

[@dmiradakis]

Can confirm, I’ve been sucked in.

[@SirusStarTV]

It's interesting that for someone it's entertainment but for others it's boring af

[@n3vin192]

Same.

[@recnepSpencar]

Been using Cypress for a year. Absolute game-changer over Selenium, webdriverio, and protractor.

[@StEvUgnIn]

Those tools are not for testing but for scraping

[@riddixdan5572]

have you ever looked into Playwright? if so, what are your thoughts?

[@rasmusfalk-jensen8221]

@@StEvUgnIn That is just not true. Both WebdriverIO and Protractor were built for testing purposes. While Selenium might just be a tool for browser automation, it has seen wide use for testing purposes as well.

[@recnepSpencar]

@@StEvUgnIn You’re not wrong that it can be used for scraping. Any E2E tool would do the trick well. It’s primary purpose thing is testing. Puppeteer is more what you’re thinking of for scraping.

[@SpinnedRock]

So if I am still using selenium, you would recommend me to change to cypress? ;-)

[@Tygrysek_]

Cypress is pretty fun, but sometimes really tricky. The funniest part of it for me was when I had to do conditional testing, and I was new to Cypress. I relied on the docs and I found a section for conditional testing. It states: "don't worry, there are ways you can do with conditional testing! for example, you can... remove the need to do conditional testing!" Thank you Cypress, very cool. PS: No, I couldn't do that

[@andreas543]

Suggestions for 100 second tuts: - Oauth2/OpenID Connect - Swagger/OpenAPI 3 - Logging/Monitoring - Caching solutions - Phaser 3

[@Attinderpal]

SAML?

[@yonatancohen7642]

julia

[@rubekjoshi]

GSAP too

[@Kyle-xk2rb]

WebRTC

[@heberjulio6303]

Lisp

[@MisterAndreSafari]

I have to say it again: your „video-editing“ and „story-telling“ skill is OUT of this world 😄 Thank you so much for your work 🙏

[@vicradon]

Thank you Jeff for another amazing 100-second tutorial. Anytime Jeff explains a concept, it becomes easier and more approachable for me.

[@JohnBrandon]

I will almost certainly never use this, but the clarity and quality of your videos is so outstanding that I can’t get enough. Thanks!

[@shaneckel]

This is the first time I've ever responded to a KZbinr request ever in the decade of watching KZbin videos but yes, I would like to see more algorithm videos. Excellent explanation of the search. This feels weird. Great work on everything you post.

[@deathlight128]

Cypress is awesome! I've spent more time debugging the jest config than testing the code base !

[@darkknightdks]

Absolutely love your videos. I have been using Cypress for over a year now and I don't want to go back to those Protactor, Selenium stuff. Also, Cypress has something called `data-cy`, which is added to the elements that you want to loop up in your tests. `data-cy` parameter can have a unique name and enables the test to directly find the element in the dom. This is an amazing feature that we use everyday and avoid looking up using html and css tags as they can change.

[@PfhorShark]

Been using cypress for 3 years after using selenium for god knows how long. I highly recommend this for TDD, your feedback cycle is almost immediate, you aren't coupled to chrome/driver versions, it's altogether the best way to write your integration tests first, see them not work, then repeatedly do the next thing it said didn't work. Simple.

[@erick289777]

Did you solve the lack of support of iFrame and multitab from Cypress?

[@nathanlamaire]

Good thing about using these tools is that it also helps you to narrow down use-case of the application you make and only implement essentials.

[@nicolasramos7084]

I've literally started working with cypress for our application at work this morning. Awesome timing as usual

[@savaasio]

the line "to figure out precisely why your code sucks" is so hilarious to me

[@rajanlalala]

😁

[@WebDevYTLearningAccount]

Thank you for the quick video. I am on a different team temporarily and this helps me better understand the purpose since I have mostly written backend code.

[@TomDoesTech]

You forgot to add the part about nobody ever maintaining the tests

[@MrBloodySpirit]

For me, I moved from Cypress to Playwright. It's much faster and can do almost everything Cypress can!

[@JPeetjuh]

That, and, so much of Cypress bugs me. Its Promises are not actual native browser Promises and can't be awaited. The magic strings for assertions. And if I wanted to see how many rows a table has, then submit a form and check if that table now has count + 1 rows, Cypress seems to actively hinder me. I found Playwright much more intuitive, friendly and robust. The only thing I really liked about Cypress was its execution window where you could "time travel" as Jeff says.

[@threewestwinds]

​@@JPeetjuh The promises thing is super annoying, and agree that the magic strings are not my favorite way of doing assertions. Even though it has a promises-like API, Cypress is actually a command queue, not a promise chain. The use of promise-like syntax (and especially the docs trying to say it's promise-based) is very misleading, 100%.

[@graffhyrum]

The cross domain restrictions and local single threading are also pretty annoying.

[@twiceagames]

is it free and can run locally? genuine question, no bias or fan boy thing.

[@seantillman7490]

I just started testing with Cypress this year, it's been real cool to use. Thanks for the videos as always!

[@danisnicee_]

How's it going so far man?

[@CodingWithLewis]

Cypress is seriously such a game changer

[@SoreBrain]

Starting into web development is great especially when you are able to enjoy such amazing content

[@mstjepan7237]

Litteraly started learning Cypress yesterday, its so amazing for testing

[@OfficeArcade]

I’m a big cypress advocate. Absolute game changer!

[@SpongeAndLeo]

Been using cypress for 4 years. It's incredibly powerful and I love it.

[@edgarhnd]

I was about to launch my app to production without testing at the end of the week.. Thanks, that seems to be exactly what I need !

[@joshuaokoro9447]

From my experience using Cypress, I can see it really makes testing fun. For me, the fun part is watching Cypress run the test and everything passes. Definitely give it a try if you haven’t. Might end up loving it

[@galgrunfeld9954]

I've been avoiding learning testing for years just because it was so boring for me. Even when I sat down with myself and asked myself what technologies I should learn to become a better well-rounded full-stack developer, testing was in there, but was always the last one I wanted to do. So I learned a few technologies, but never picked up testing. But this framework makes me actually want to learn it, seems so cool!

[@joshuaokoro9447]

@@galgrunfeld9954 I ran away from testing for so long until I started seeing the importance. Especially working with a team with constant update, testing would catch a lot of bugs before it gets to staging or production. These frameworks have made it enjoyable so that’s a bonus. Funny thing, I’m the one now rooting for testing

[@galgrunfeld9954]

@@joshuaokoro9447 yeah, I'm very much aware of the benefits. Luckily, or maybe not, I so far worked only in small teams and did a lot of things independently so TDD wasn't much of a necessity, but I can definitely see it being crucial in so many places.

[@damar1967]

100 Seconds video ideas: - Backing up hard drive - Wiping history - Getting some RAM a few megabytes - Logging in and logging out

[@brightpixeluk]

Been using Cypress with TestingLibrary and MSW for a while and they are great for getting tests done fast.

[@mahmudzaman5445]

Really cool. Planning to use it on my next side project.

[@vnm_8945]

I worked as an automation tester using Cypress, it was cool.

[@jon1867]

If it were me, I wouldn't use it for unit or integration tests. But it's amazing for UI or E2E tests

[@skriptkid4292]

this is awesome, i didnt even know what cypress was 100 seconds ago

[@logichog4181]

thanks for this one bro, I needed it

[@moazahmed5388]

I've just experienced my first BSOD for a while , while watching this video. it makes sense now .

[@connorallen162]

It's funny how I watch these videos once and I'm like "that's neat" then a month later I'm like "wait if I actually used that it could absolutely transform my development workflow!"

[@konnilol4]

I like how it just isn't "if" or even "when" anymore but straight up "why your code sucks"

[@recker7017]

this channel is becoming very js oriented

[@weikeshi1788]

Just started to write tests for my project, and see this today

[@siydge]

My bud who I work with is from Cyprus, he's going to go crazy after seeing this video... Likely for both the name and what it does.

[@devmeta1478]

Okay, I guess my company just made another decision and that is which testing tool to use for front-end. :D Thanks Jeff

[@RemX405]

This and TestCafe make E2E an absolute breeze for any web dev.

[@aylictal]

I had to make the choice of using testcafe over cypress for my company 3 years ago. Main reason was cypress didn't support safari, nor s.

[@aryasaktiflister_aw]

idk what a rails dev like me is watching this for but that looks cool

[@mohammadfarhanr6650]

This content is always awesome. I am always curious how you can manage so many different techs, do you have experience using them throughout your career? Or do you just learn it like 1 week and make a video of it? or how? I am always amazed by how you deliver your content.

[@ibadsiddiqui1]

just what I needed! 🤩

[@jacobshuman1650]

I’d love one of these videos for playwright! I tried cypress and while it was really cool (especially with the test runner) it felt a bit dated imo. The lack of native promises really hurt my experience.

[@rtemis9016]

finally found what I needed. thanks Jeff !

[@amoodaa]

We've ended up using playwright instead of cypress, had some problems with ts with cypress, and playwright setup was just smooth as butter

[@PBKB]

I'm using Playwright. Amazing tool. Build a suite to test all our countries (work for a B2B supplier)

[@PhilipAlexanderHassialis]

Excellent video as always! And now that you are delving into test territory, how about a nice vitest in 100 seconds? I think its time!

[@its_vincesanity]

I really love cypress ❤️ Even now I have to use React, I feel save to delivery some quality 🙌🏻

[@BillyHudson1]

This video got me into cypress, pretty f-n dope. I still need testing for Electron tho so I'm using Playwright since Spectron just got deprecated. Need to decide if I should switch from Mocha to Playwright Test as my Electron test runner.

[@BillyHudson1]

Though reading these comments maybe the right choice is to go full on playwright. I'm still investigating. I do like how cypress works but obviously a lot of the pain points I hit already are a common thread.

[@Zandercraft]

"To figure out precisely why your code sucks..." Lol! I feel called out for some reason.

[@MineToaster12]

I prefer playwright over cypress, it's more robust though ofc looks less fancy than cypress. What cypress killed for me is them not support any http/3

[@HankyAd]

I really like using Playwright, but it just doesn't work in CI for more than a week before something explodes and it stops building I should look into putting it into a docker container

[@EricSundquistKC]

Also left Cypress for Playwright, as getting our auth in all the tests was a nightmare in Cypress

[@threewestwinds]

Cypress's coming support for cross-domain communication (and the Sessions API) should make auth a lot less painful. Of course, "It's coming" is not the most useful answer. ^^;;

[@awabqureshi814]

I'd love to see a purescript video! Maybe even a beyond 100 seconds on it too.

[@evanhruskar]

I've been waiting for this video. The automatic loading feature doesn't always work properly (doesn't work for XHR requests). But It's 100x better than Selenium. Highly recommended.

[@rafsoverflow]

I'm trying my hardest to dig myself out of tutorial hell but you keep making these awesome videos that make me want to dig myself deeper. Fireship is not good during tutorial rehab.

[@Gautamogg]

Next video should be “Types of tests” in 100 seconds.

[@_sevelin]

What a coincidence, I was learning Cypress right now already.

[@diogo405]

Liking before watching 👍🏽

[@Wangssta]

Is it realy a legit way to do tdd and replace unit tests on frontends? So there would be a unit test and e2e test section in your cypress folder? I somehow like the idea but it doesnt feel natural 😂

[@UselessDuckCompany]

I hear html over the wire is coming back, any news on that?

[@Dima1415]

Isn’t that just rendered html on the server? He definitely covered many frameworks that focus on that like nextjs. HTML over the wire has never stopped being a thing really.

[@dadsfads]

Can you do one on Cypress Hill next?

[@diegolikescode]

good content, as always.

[@shlemekian]

Currently trying to decide between Cypress and Playwright for e2e testing on a large project at my job. What's the chance you have a playwright video on the way? :) Great stuff as always.

[@dinosaric4862]

Love your videos!

[@nullpointer1755]

Can you make a video about Data Oriented Programming and ECS (Entity Component Systems) ?

[@itsadira007]

Are you fucking psychic, just needed this ❤️

[@LiamODev]

I was struggling with something in webdriver and it looks like Jeff and the Algorithm (good name for a band) delivered Just In Time ;)

[@masrafirinvi]

Helpful! Thank you so much❤️

[@hellohabibi1]

Holy, thats so epic!

[@kristofgilicze]

I like Cypress, it really does work like a charm. One thing to note is that the Electron runtime is bundled / baked in, which arguably is pretty stupid. There is no way to install Cypress headless, even though most people use a real browser to run tests.

[@DaraulHarris]

> There is no way to install Cypress headless I was wondering how I might use it to do my automated testing in gitlab-ci. The docs mention being able to do this, though.

[@threewestwinds]

@@DaraulHarris Cy can absolutely run in CI. Doing an npm install also downloads the cypress binary, which is fairly large, and comes with electron baked in.

[@davloche6763]

There is a headless mode for your tests 😉

[@kristofgilicze]

There is headless mode, though Electron included no matter what. The "slim" docker CI image is roughly 600 mb. To be fair this includes Chrome and FF also.

[@TheDogn]

0:35 precision is important in these matters.

[@amy2technology87]

I enjoy your background classic. Where Can I found it?

[@owenwexler7214]

My company would not have gotten testing done as quickly as we did without Cypress.

[@ArnavSingh-im5bj]

More about cypress please and also about load testing of APIs

[@eliascotrim51]

What are the advantages of something like Jest compared to Cypress?

[@futballboy101]

Do a video of cucumber bdd integrated with cypress. This brings the three amigos together and speak the same language. Let me know if you’d like some insight as to why this approach is amazing.

[@erik9817]

Nice! Does any of you Cypress pros know if it allows for checking the order or Redux actions in the Redux Chrome tab?

[@tyrizzle3]

Do one of your things on R! I don't think I'm allowed to say I know how to code till you do 😅💪👍🧠

[@neonai9213]

maybe do some more non-frontend-oriented stuff like neural networks (tensorflow, pytorch) or some other interesting stuff like a turing machine

[@spencjon4822]

'Love Cypress, highly recommend

[@nadavbarsheshet2512]

Thank you! Can you please do Julia next?

[@DogeMultiverse]

Was just looking at javascript testing! How do you always come up with timely content? Thanks again!

[@manavsharmaer]

Please make some videos on load testing tools

[@Patrickdaawsome]

Playwright is a great lowkey Cypress alternative.

[@DevAcademyCom]

I hope you enjoy the free Web E2E testing course! 🔥 courses.dev-academy.com/p/web-e2e-testing

[@parthipankalayini8]

Sir, waiting for more rust lang and golang videos 🙌

[@alfredogrande413]

Same here

[@spongechameleon6940]

Rust and *elixir videos

[@stolensentience]

great vid, obviously. but what folder/file icon theme is that?

[@GlitchyPSI]

wow OK cypress looks super cool

[@ChemistTea]

If I was to create a small (small-medium) single-page app in React, would Cypress be a good choice? Or is it better to stick to Jest, since it comes ready with create-react-app. If I had to pick one. I might play around with this later, UI tests feel more accurate to what user actually experiences. But pre-build Jest is like there already, so it's easy.

[@albirtarsha5370]

Cypress on the front end; Jest on the back end.

[@ChemistTea]

@@albirtarsha5370 Is React used in back end? I haven't heard of that.

[@albirtarsha5370]

@@ChemistTea No, but if you had a node back end to interact with, then Jest would be a good way to test any complexity. On the front end if you are testing multi-page processes then Cypress will shine. Like if your user first does a sign up, then a login,, then some interactions, then a log out, Cypress can test that process end-to-end.

[@adambickford8720]

@@ChemistTea Hes just blindly shouting his biases. Stick to whats in the box, its 99% the same and the 1% isn't likely worth the effort.

[@TheMrBvcx]

Fireship is a modern hero

[@Im_Ninooo]

that's incredible!

[@snaekboi]

Can we have Spark / Hadoop next please :)

[@RobertoDuransh]

awesome tool TY for this... btw i love to see fastApi in 100 seg

[@karisnjiru8245]

Nice I was thinking of testing

[@emstudios14]

This is so cool.

[@reggiemate7288]

Now I will defs test my own projects /s

[@astomero]

that's quite insane I am not gonna lie

[@williammoriarty3402]

Here is a sincere suggestion, can you please do one on julia?

[@travispulley5288]

I tend to use puppeteer for everything, and I've used cypress, but what exactly are the advantages over puppeteer for testing? Is it the structure/interface and framework? Can/should I use both together?

[@threewestwinds]

Biggest advantage over puppeteer is the builtin retries / waiting for the page to settle. No more explicit need to wait for a loading spinner to be gone - just assert the content is there, and Cypress will retry until it is or until the command times out. This sort of functionality is built into basically every command. It's amazing the amount of "just works" you can get out of that.

[@travispulley5288]

@@threewestwinds there are different meanings of a page having settled (DOMContentLoaded event? network idle?) , and puppeteer has them all covered. Messy wait techniques are why I quit using selenium, but that's not something puppeteer lacks at all

[@threewestwinds]

​@@travispulley5288 By "page to settle'" I don't just mean during page load events - I mean every command you issue, which causes rerenders as data loads in, spinners, animations, outgoing requests. Using Cypress you usually don't even need to *think* about waiting at all. I just assert or act on the desired end state. You can click on buttons that don't exist yet, and Cypress will wait until the button exists and then click on it. It's been a couple years since I used Puppeteer. But this was the biggest benefit for me. No 'filler' commands (like "wait for element to exist, then click on it"). You just say what you want. Less code, less mental effort.

[@travispulley5288]

@@threewestwinds pptr has all these wait styles baked into everything. If you're trying to interact with an element that's not present, it's helpful to know that it's not present and to treat that as an error (and/or wait for the implicit timeout). Even with my lack of Cypress experience, I know you'll just end up waiting for the max timeout duration in those cases anyways if the element never appears. What I'm getting from this is that they both do the same thing, but cypress has a friendlier companion UI? I need to do more research.