@@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**
@@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.
@@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.
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
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.
@@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%.
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.
This is the first time I've ever responded to a CZcamsr request ever in the decade of watching CZcams 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.
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.
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.
> 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.
@@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.
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.
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
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. ^^;;
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
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!
@@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
@@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.
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.
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.
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!"
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.
E2E test is great if used properly. Never test all the things only with E2E. Make a lot of unit and integration tests. Then, test the end-user journey with E2E test.
@@tomascarignano5002 It's mostly about cost, e2e test take longer to run, longer to develop, are more brittle (prone to failure) and more time consuming to maintain than integration/unit tests.
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.
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.
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.
I'll add it to my list of the 8 trillion Javascript tools and frameworks I still need to evaluate lol Jokes aside I will probably check this out first since it actually looks super useful
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.
Ah yes, automated UI testing. That thing I'm definitely absolutely positively going to start doing... one of these days.
I have never seen a comment I relate more with.
I basically exclusively test network calls using cypress these days. Powerful framework.
Meet converted pyramid, tapes server and unit size discovery.
So all your PR's get accepted with 0 unit tests?
@@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**
Suggestions for 100 second tuts:
- Oauth2/OpenID Connect
- Swagger/OpenAPI 3
- Logging/Monitoring
- Caching solutions
- Phaser 3
SAML?
julia
GSAP too
WebRTC
Lisp
Been using Cypress for a year. Absolute game-changer over Selenium, webdriverio, and protractor.
Those tools are not for testing but for scraping
have you ever looked into Playwright? if so, what are your thoughts?
@@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.
@@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.
So if I am still using selenium, you would recommend me to change to cypress? ;-)
I don’t even do web development but these videos are just too entertaining
Can confirm, I’ve been sucked in.
It's interesting that for someone it's entertainment but for others it's boring af
Same.
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
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 🙏
Thank you Jeff for another amazing 100-second tutorial. Anytime Jeff explains a concept, it becomes easier and more approachable for me.
For me, I moved from Cypress to Playwright. It's much faster and can do almost everything Cypress can!
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.
@@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%.
The cross domain restrictions and local single threading are also pretty annoying.
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.
Did you solve the lack of support of iFrame and multitab from Cypress?
Cypress is awesome! I've spent more time debugging the jest config than testing the code base !
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!
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.
This is the first time I've ever responded to a CZcamsr request ever in the decade of watching CZcams 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.
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.
the line "to figure out precisely why your code sucks" is so hilarious to me
😁
I've literally started working with cypress for our application at work this morning. Awesome timing as usual
Cypress is seriously such a game changer
I just started testing with Cypress this year, it's been real cool to use. Thanks for the videos as always!
How's it going so far man?
I like how it just isn't "if" or even "when" anymore but straight up "why your code sucks"
I’m a big cypress advocate. Absolute game changer!
This and TestCafe make E2E an absolute breeze for any web dev.
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.
idk what a rails dev like me is watching this for but that looks cool
Litteraly started learning Cypress yesterday, its so amazing for testing
Starting into web development is great especially when you are able to enjoy such amazing content
100 Seconds video ideas:
- Backing up hard drive
- Wiping history
- Getting some RAM a few megabytes
- Logging in and logging out
You forgot to add the part about nobody ever maintaining the tests
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.
> 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.
@@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.
There is a headless mode for your tests 😉
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.
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
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
Also left Cypress for Playwright, as getting our auth in all the tests was a nightmare in Cypress
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. ^^;;
Been using cypress for 4 years. It's incredibly powerful and I love it.
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
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!
@@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
@@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.
If it were me, I wouldn't use it for unit or integration tests. But it's amazing for UI or E2E tests
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.
this is awesome, i didnt even know what cypress was 100 seconds ago
I worked as an automation tester using Cypress, it was cool.
"To figure out precisely why your code sucks..."
Lol! I feel called out for some reason.
Really cool. Planning to use it on my next side project.
thanks for this one bro, I needed it
just what I needed! 🤩
Just started to write tests for my project, and see this today
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.
this channel is becoming very js oriented
Next video should be “Types of tests” in 100 seconds.
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.
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!"
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 !
I've just experienced my first BSOD for a while , while watching this video. it makes sense now .
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.
Been using Cypress with TestingLibrary and MSW for a while and they are great for getting tests done fast.
Fireship is a modern hero
E2E test is great if used properly. Never test all the things only with E2E. Make a lot of unit and integration tests. Then, test the end-user journey with E2E test.
Could you explain real quick why?
@@tomascarignano5002 It's mostly about cost, e2e test take longer to run, longer to develop, are more brittle (prone to failure) and more time consuming to maintain than integration/unit tests.
Sir, waiting for more rust lang and golang videos 🙌
Same here
Rust and *elixir videos
*fireship on forms: hi mom
Okay, I guess my company just made another decision and that is which testing tool to use for front-end. :D Thanks Jeff
My company would not have gotten testing done as quickly as we did without Cypress.
finally found what I needed. thanks Jeff !
I'd love to see a purescript video! Maybe even a beyond 100 seconds on it too.
I'm not sure I need a sophisticated tool to tell me my code sucks, I have co-workers for that!
This is so cool.
This is why I develop command line utilities.
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!
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.
Love your videos!
Cypress is love. I don't wanna touch Selenium ever again.
What a coincidence, I was learning Cypress right now already.
I'm using Playwright. Amazing tool. Build a suite to test all our countries (work for a B2B supplier)
Playwright is a great lowkey Cypress alternative.
We've ended up using playwright instead of cypress, had some problems with ts with cypress, and playwright setup was just smooth as butter
I want to clarify that in many SPA projects, cypress is a bad choice, leads to flaky tests. I'd recommend playwright if you use react and etc.
0:35 precision is important in these matters.
"Fun" "Javascript" "Testing" choose one
Was just looking at javascript testing! How do you always come up with timely content? Thanks again!
I really love cypress ❤️ Even now I have to use React, I feel save to delivery some quality 🙌🏻
Can you do one on Cypress Hill next?
I hope you enjoy the free Web E2E testing course! 🔥
courses.dev-academy.com/p/web-e2e-testing
Liking before watching 👍🏽
I was struggling with something in webdriver and it looks like Jeff and the Algorithm (good name for a band) delivered Just In Time ;)
Video idea: HTML over the wire frameworks
'Love Cypress, highly recommend
What are the advantages of something like Jest compared to Cypress?
Are you fucking psychic, just needed this ❤️
good content, as always.
I hear html over the wire is coming back, any news on that?
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.
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.
These little jabs always make me laugh 0:39 😂
Can you make a video about Data Oriented Programming and ECS (Entity Component Systems) ?
I'm just here to see all the people who _just_ started learning Cy
now, let's do a "playwright in 100 seconds" and then a "cypress vs playwright in 100 seconds" 👀
I'll add it to my list of the 8 trillion Javascript tools and frameworks I still need to evaluate lol
Jokes aside I will probably check this out first since it actually looks super useful
Cypress for UI and PactumJS for API
I got excited because i thought this was a minimentery about the nation of cyprus.
Helpful! Thank you so much❤️
that's quite insane I am not gonna lie
Impressive! R in 100 seconds please
wow OK cypress looks super cool
Vitest in 100 seconds next!
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.
Playwright in 100 seconds
More about cypress please and also about load testing of APIs
Now I will defs test my own projects /s
Assembly in 100 Seconds maybe? :)