This is insanely useful. I regret not learning how to do testing 1.5 years ago. It would have saved me hours, if not days worth of time in testing manually
Scratch that, think about the time you would've saved while debugging errors on the e2e layer! Unit testing forces you to separate your code into small chunks and test everything as soon as possible. Crazy useful skill!!
For someone who wants to take a look at the overview before dive in the specific part. I really appreciate the way you write your description: Extremely useful
Two years and 180,000+ views later, but on the off chance you see this.. THANK YOU. I have never seen a tutorial so well put together easy to understand. As a self taught developer over the last 9 months I cannot believe I have never seen your videos before. Please keep it up!!!
Best unit testing from the ground up I've seen so far on all the world wide interwebs! Been paying for tutorials, searching high and low... Thanks for putting this together beginning with testing a most BASIC function that returns only a string concatenated value. This is what I've been looking for!!! The one thing I don't see anyone doing (neither professionally nor in any demonstration) is to combine debugging with unit testing functions. My biggest benefit to TDD is to setup the expectation prior to writing the function and write the function to satisfy that. That way, I am testing mostly functions only and, by the time it's completed to satisfaction, the test enforces the outputs from the function. The test is done and the function is done. I do not understand why more developers do not work this way.
A genius instructor in the world. Now I have no fear in JavaScript. U made my development journey so simple and interesting. Thanks a lot from bottom of heart.
For anyone having issues with the end to end test not completing the automated test at around the 35:00 minute part it is simply because Jest is timing out and you just need to refer to 38:29 to fix that.
It's one of the best quick and comprehensive guides around the different levels of test automation. Well done mate, and please guide me if you have any similar videos in your channel that I missed.
i wanna mention something there is a long while since i watched a video in your channel and wanna say that you get so much better at explaining and you feel much more confident and experienced keep the good work up Thanks for this fruitful content
I can't find a better introduction course to testing. I've been struggling for far to assimilate testing. I'm currently taking a course on the topic but I still can't get the whole thing. With this video, everything I previously learned has become clearer, and now I can make a clear way to progress and fully conquer testing. Thank you so much @Maximilian
Great vid, thank you Max. I need to disagree with one thing tho. 32:00 - "async/await does it (then and catch) for you" async/await doesn't catch errors. You would need to additionally use `try {} catch (e) {}` and await within try block in order to catch errors from the promise.
It is thanks to this video (and to a test I wrote for validateInput) that I can say, the "+text === NaN" check in the validateInput function always returns false. So if I send "isNumber: true" to the function, and as text input "12e", it would consider it as a valid age. Using "isNaN(+text)" solves that. Thank you, Max, for such a great introduction to js testing!
That was a GREAT introduction to testing man. I love how you explain things in theory and using slides before the actual practice. It gives us a better context on what we're doing. Thanks :)
Max, i'm a student of your Udemy courses. This video was great, because i didn't understand how integration tests and e2e tests works. You're always able to explain the things in a simple way. Thank you Academind.
This is a brilliant video about testing and is definitely a must for devs trying to learn to test their codes for the first time. I am super glad there is a video this clear that does not expose unnecessary complexity of other modules are not required to do testing. Its focus on testing and its conciseness made me understood the three types of testing in only one watch. Sincerely, thank you.
Hi Max, thanks for the video, at 17:00, how did the recommandations pop out automatically? what did you do there? My VSC doesn't pop out recommandations automatically.
I just like this dude. He's always happy. Although it pretty normal to express some happiness when making UA-cam videos, however, there's something different about his. Wish I could meet him one day. More power to your elbow.
I'm really impressed each time I'm looking for new things or concept to understand and explore because I'll always find you either on udemy or youtube video answering questions I've been asking myself about some vocabulary point I did get quite well. For couples of weeks, I've been trying to understand : - testing, - thinking about when and where to add typescript and what to test ( as working with jest we should only assert output instead of type, which typescript should do instead I reckon ) - that there were few kinds of testing, - that actually I was not grasping the difference between unit testing, functional testing, integration testing and where was E2E in all that ( ends up with E2E was actually functional testing ( and not hard-related to test one function ), unit test was actually this kind of test where you actually test one function ) , then got lost with integration test. Your explanation was confirming some though and also made me understand better what was integration tests : testing function with other dependencies ( == other functions ). Can't wait to go deeper and make it to the tests automation. Thanks again for your explanation
That's an amazing crash course about testing in JavaScript, it's so complete, I really enjoyed watching it, I've learned lots of things about testing thanks to Max, So Thank you so much, Max for this awesome crash course, You're the best💙🥰🙏🌹
As usual you are the most reliable instructor to depend on. I am enjoying your videos on Udemy. Waiting for many more videos on this topic that will help me in pure TDD and inculcate TDD approach in true sense. Thanks Max 🙂
21:22 - The first test success indicates a "false negative", not a "false positive". False positive means that the test is failing but is not really a valid failure (for e.g. random failures). In your example, it is a false negative - test is passing, even though there's a problem with the code.
In React case, what should I use? For Unit and Integration Tests: - Jest + (enzyme or react-testing-library) For e2e tests: - Puppeteer or Cypress? Great video, thanks for sharing!
Yes that's sound about right. You can't test React Hooks using enzyme which is why react-testing-library is getting popular, and it's actually pretty good.
Max, I guess it would be a great idea to create a full course about testing, maybe using TDD, some React testing and so on. This is a course I wanna see from you so much and I hope, that one day it will become true ;)
3 years here, haha. Like someone else pointed out: The Boy Scout Principle works wonders. Leave everything better than you found it (i.e. everywhere you visit, you create tests for it)
i love you max, you're great man, i've gor your react, react native, nodejs and mern courses on udemy, and i never wanted to learn about tests but now im learning and youre great man
Max's tutorials are great! I noticed when he hovers over a function, like "test()", he gets extra info about that function, and also extra methods. Prime example of both at 17:00. I get that for some packages, but not others. Any tips how to fix this?
TU (Thumbs Up, Thank You, THE Ultimate) ! Remark to readers: This of course is only an introduction about testing and not about TEST DRIVEN development, perhaps you can add a remark at the end of the vid saying that.
33:00 my chrome test browser closes after displaying the page for a really short time. It isn't staying open like in the video, anybody having the same issue ? By the way I'm using windows 10.
Thank you for the great video. Can you help of point me to how I can unit test for a number of sets of inputs? Something like {{anna, 28}, {nick,55},{Sam,22}}. I think it is called Parameterized testing?
I have a question about adding "--coverage" into your jest script in the package.json. Since --coverage will break down the function into each step. Is it still necessary to use integration tests then?
Loved that you used puppeteer too! Cypress is a nice tool to use very similarly as well. The only thing I saw missing was integration tests for api and integrations. Would love to see that!
I am very confused. I am currently writing the tests the way you do, but I mock all the dependencies, because I don't want to create tighly coupled tests. Otherwise, if I change unit implementation, I would have to check more than 2 tests. However, I saw some talks about TDD and how we should do testing and they tell us not to test implementation but behavior. If those functions are in a module, then should I really test them? Should I not test then only the output of the module?
11:50 - unit testing
23:10 - integration testing
29:23 - e2e
my man
ty weeb :D
thank you
The Bikini Bottom thanks you
Thank you :D
This is insanely useful. I regret not learning how to do testing 1.5 years ago. It would have saved me hours, if not days worth of time in testing manually
Scratch that, think about the time you would've saved while debugging errors on the e2e layer!
Unit testing forces you to separate your code into small chunks and test everything as soon as possible. Crazy useful skill!!
For someone who wants to take a look at the overview before dive in the specific part. I really appreciate the way you write your description: Extremely useful
Two years and 180,000+ views later, but on the off chance you see this.. THANK YOU. I have never seen a tutorial so well put together easy to understand. As a self taught developer over the last 9 months I cannot believe I have never seen your videos before. Please keep it up!!!
Best unit testing from the ground up I've seen so far on all the world wide interwebs! Been paying for tutorials, searching high and low... Thanks for putting this together beginning with testing a most BASIC function that returns only a string concatenated value. This is what I've been looking for!!!
The one thing I don't see anyone doing (neither professionally nor in any demonstration) is to combine debugging with unit testing functions. My biggest benefit to TDD is to setup the expectation prior to writing the function and write the function to satisfy that. That way, I am testing mostly functions only and, by the time it's completed to satisfaction, the test enforces the outputs from the function. The test is done and the function is done. I do not understand why more developers do not work this way.
By far the best (free) intro to testing video I've seen on the web. Thank you Max!
Awesome to read that Jin, thanks a lot for your great feedback!
You're awesome you always give us what we want. Thanks for sharing your knowledge Max
Thank you very much for your support Ibrahima :)
BLM
A genius instructor in the world. Now I have no fear in JavaScript. U made my development journey so simple and interesting. Thanks a lot from bottom of heart.
I usually don't leave comments but this is really high quality. Thanks a lot!
Really high quality video - both the content and the form (some graphs when needed, some code when needed). Thanks!
So happy to read that, thank you Jack!
For anyone having issues with the end to end test not completing the automated test at around the 35:00 minute part it is simply because Jest is timing out and you just need to refer to 38:29 to fix that.
It's one of the best quick and comprehensive guides around the different levels of test automation.
Well done mate, and please guide me if you have any similar videos in your channel that I missed.
i wanna mention something
there is a long while since i watched a video in your channel and wanna say that you get so much better at explaining and you feel much more confident and experienced
keep the good work up
Thanks for this fruitful content
I can't find a better introduction course to testing. I've been struggling for far to assimilate testing. I'm currently taking a course on the topic but I still can't get the whole thing. With this video, everything I previously learned has become clearer, and now I can make a clear way to progress and fully conquer testing. Thank you so much @Maximilian
Great vid, thank you Max. I need to disagree with one thing tho. 32:00 - "async/await does it (then and catch) for you" async/await doesn't catch errors. You would need to additionally use `try {} catch (e) {}` and await within try block in order to catch errors from the promise.
It is thanks to this video (and to a test I wrote for validateInput) that I can say, the "+text === NaN" check in the validateInput function always returns false. So if I send "isNumber: true" to the function, and as text input "12e", it would consider it as a valid age. Using "isNaN(+text)" solves that. Thank you, Max, for such a great introduction to js testing!
This is so coherent and well structured for providing an introduction. Thanks for the awesome video.
Green is a beautiful color! Thanks Max for the tutorial.
That was a GREAT introduction to testing man. I love how you explain things in theory and using slides before the actual practice. It gives us a better context on what we're doing. Thanks :)
Max, i'm a student of your Udemy courses. This video was great, because i didn't understand how integration tests and e2e tests works. You're always able to explain the things in a simple way. Thank you Academind.
Thanks so much for your wonderful feedback Rafael, happy to read that you like my explanations!
Your explanation with specific code is very easy to understand.
I appreciate it.
Thank You, I learned so much. It seems like JS testing is now one of the must haves when applying for jobs these days.
Thanks a lot, happy to read that the video was helpful!
Things become so clear after having your videos. Thank you Max
This video will still be relevant in 2030! Thanks you very much.
Your videos are great! Very often use them to learn/refresh/structure information. Thank you very much for your work!
Happy to read that Ekaterina, thank you!
Great Max, maybe the best teacher existing about programming languages!
This is a brilliant video about testing and is definitely a must for devs trying to learn to test their codes for the first time. I am super glad there is a video this clear that does not expose unnecessary complexity of other modules are not required to do testing. Its focus on testing and its conciseness made me understood the three types of testing in only one watch. Sincerely, thank you.
Great thanks Max, it helps me understand the javaScript testing better than just reading a document. Now I will go and learn more on using Mocha.
Thank you Max! Nicely organized video. I watched it several times :)
Hi Max, thanks for the video, at 17:00, how did the recommandations pop out automatically? what did you do there? My VSC doesn't pop out recommandations automatically.
Oh I figured it out. stackoverflow.com/questions/42024526/vscode-automatic-type-acquisition-for-jest. Cheers!
I just like this dude. He's always happy. Although it pretty normal to express some happiness when making UA-cam videos, however, there's something different about his. Wish I could meet him one day.
More power to your elbow.
Thanks a lot Alexeis, I would indeed say that I'm a quite happy person, cool to read that is also visible in the videos!
I'm really impressed each time I'm looking for new things or concept to understand and explore because I'll always find you either on udemy or youtube video answering questions I've been asking myself about some vocabulary point I did get quite well.
For couples of weeks, I've been trying to understand :
- testing,
- thinking about when and where to add typescript and what to test ( as working with jest we should only assert output instead of type, which typescript should do instead I reckon )
- that there were few kinds of testing,
- that actually I was not grasping the difference between unit testing, functional testing, integration testing and where was E2E in all that ( ends up with E2E was actually functional testing ( and not hard-related to test one function ), unit test was actually this kind of test where you actually test one function ) , then got lost with integration test.
Your explanation was confirming some though and also made me understand better what was integration tests : testing function with other dependencies ( == other functions ).
Can't wait to go deeper and make it to the tests automation.
Thanks again for your explanation
Finally, I learned JS Testing
Same here! The book wasn't enough thus this video is a savior!!! Thanks a lot, made it breif and clear!
Best video on testing I've seen so far, clear and detailed. thank you so much for sharing!
Max, can't thank you enough for your awesome videos! I learn best by clear explanation and example--your excellent teach style does both. Thank you!
I would say for every developer:
"The most valuable courses you can see here on Academind"
Thanks a lot Max :)
Wow, that is awesome to read Mostafa, thanks so much!
Just loved it, best tutorials all over the web man
Thanks Max, you're really the king of teaching. Thank you for so much value in your videos. Please keep it up!
That's an amazing crash course about testing in JavaScript, it's so complete, I really enjoyed watching it, I've learned lots of things about testing thanks to Max, So Thank you so much, Max for this awesome crash course, You're the best💙🥰🙏🌹
As usual you are the most reliable instructor to depend on. I am enjoying your videos on Udemy. Waiting for many more videos on this topic that will help me in pure TDD and inculcate TDD approach in true sense. Thanks Max 🙂
best video i have ever seen that shows the differences between those types of testing
21:22 - The first test success indicates a "false negative", not a "false positive". False positive means that the test is failing but is not really a valid failure (for e.g. random failures). In your example, it is a false negative - test is passing, even though there's a problem with the code.
I think that this is the best instructive video I have ever watched.
On 27:30 you can just add this. before validateInput function call, and it should work correctly
In React case, what should I use?
For Unit and Integration Tests:
- Jest + (enzyme or react-testing-library)
For e2e tests:
- Puppeteer or Cypress?
Great video, thanks for sharing!
Yes that's sound about right. You can't test React Hooks using enzyme which is why react-testing-library is getting popular, and it's actually pretty good.
This video is from 5 years ago, but still very useful, and I think it still be for some years to come.
Really I was wondering about how testing done and then I got this video. Thanks Sir.
Your channel has helped me tremendously!
Just awesome to read that Elem, thanks a lot for your comment!
This video is awesome! It perfectly shows the three most common types of testing. Thank you very much Max for sharing this!!
Happy to read that the video was helpful for you, thanks a lot for your comment!
Max, I guess it would be a great idea to create a full course about testing, maybe using TDD, some React testing and so on. This is a course I wanna see from you so much and I hope, that one day it will become true ;)
I'm afraid to watch this video for fear I'll have to refactor a years worth of work.
Same here
start with a single e2e test that actually helps you skip manual test
lol
you can implement the tests for new functions as you keep coding and them make the changes over time when you make updates to old functions
3 years here, haha. Like someone else pointed out: The Boy Scout Principle works wonders. Leave everything better than you found it (i.e. everywhere you visit, you create tests for it)
i love you max, you're great man, i've gor your react, react native, nodejs and mern courses on udemy, and i never wanted to learn about tests but now im learning and youre great man
Max's tutorials are great!
I noticed when he hovers over a function, like "test()", he gets extra info about that function, and also extra methods. Prime example of both at 17:00. I get that for some packages, but not others. Any tips how to fix this?
Excellent , what other doc/courses that you recommend for advanced unit testing ?
You are a game changer. Keep up the good work! subscribed :)
Thanks for the sub!
Straight into and out of the point. Thanks.
Another amazing tut by you. Danke dir vielmals, Max. :)
It was a very quick and understandable explanation! Anyway, now Mocha has supported assertion library too right? Correct me if I'm wrong please.
This is great stuff, thanks a lot! Would love to see other testing-related content from you Max :)
Thanks a lot Dmitry, I might indeed dive deeper into testing in future videos.
you made testing look so damn easy...i love it and want dive deep into testing !!...thank you very much sir
amazing video !!!!!!!!!!!!
An excellent walk through from concept to uses example. It helped me to get familiar with testing.
Max, thanks for this amazing video, congratulations !
Thank god it arrived!
Excellent video as usual, thank you! Most people only show unit testing and I'm like, "Yeah, but..."
This is the best testing video ever, you are a sensei
Thank you very very much Carlos, this honestly means a lot to me!
Another excellent video, as always. Thanks, Max!
Thanks a lot for your great feedback Davinir!
This video is awesome in explaining how to write and run test
@Academind How did you select at 34:14 without a mouse?
Great examples. Please more about testing.
2021: Academind still Acing with these examples :D
Thanks you so much.Make a full tutorial on that.thanx Max.
I might indeed create more content about testing in the future, but we'll see. Thank you for your comment Sourish!
If
@@academind Please continue the series.....
udemy :)
Very nice and clear. Makes want to write more unit tests. Thank you!
Happy to read that you like it, thank you for your comment!
Great tutorial as always. I know this is about 2 years old but What do you think about using Cypress for Browser testing?
If the Jest autocomplete is not coming up in VS Code, you can type 'npm i --save-dev @types/jest' and restart VS Code.
Surely ..he is a great teacher
Thanks for the nice explanation , I am back end developer but you inspire me to learn front end technology. Great :)
Happy to read that Sagar, thanks a lot for your comment!
That was an amazing video thank you so much. I loved how to showed and explained how puppeteer was working. Thank you.
Glad it helped!
TU (Thumbs Up, Thank You, THE Ultimate) !
Remark to readers: This of course is only an introduction about testing and not about TEST DRIVEN development, perhaps you can add a remark at the end of the vid saying that.
Brilliant video, thank you Max!
Wish I could like this vid 10 times
Watching two years later... And awesome tutorial nowadays hahaha
Thanks. It is a very good and simple way of diving to the testing.
Thanks a lot for your great feedback Emre!
Incredibly well explained. Thanks a ton!
So happy to read that Bartek, thank you!
Thanks a lot !! Can I know which app you used to test ?
33:00 my chrome test browser closes after displaying the page for a really short time. It isn't staying open like in the video, anybody having the same issue ? By the way I'm using windows 10.
Same issue here. Also when I told click element ref as 'input#age', I'm getting an error.
Was having the same issue. I added an await page.waitFor(10000) to keep the page open longer.
Fantastic video still in 2022!
Thank you for the great video. Can you help of point me to how I can unit test for a number of sets of inputs? Something like {{anna, 28}, {nick,55},{Sam,22}}. I think it is called Parameterized testing?
I have a question about adding "--coverage" into your jest script in the package.json. Since --coverage will break down the function into each step. Is it still necessary to use integration tests then?
Loved that you used puppeteer too! Cypress is a nice tool to use very similarly as well. The only thing I saw missing was integration tests for api and integrations. Would love to see that!
I am very confused. I am currently writing the tests the way you do, but I mock all the dependencies, because I don't want to create tighly coupled tests. Otherwise, if I change unit implementation, I would have to check more than 2 tests.
However, I saw some talks about TDD and how we should do testing and they tell us not to test implementation but behavior. If those functions are in a module, then should I really test them? Should I not test then only the output of the module?
Great video .. very well explained.. thank you Max!
Exactly what I was looking for! Very well explained :) Thanks a lot :)
automation testing is done with frameworks like appium or sellenium.
are you thinking test suite.
Thank you! I studied a lot of about Web programming with your videos. :)
So cool to read that, thanks a lot for your comment!
This was really helpful. Thanks Max.
Very clearly explained, thank you
Thanks max I was waiting this course
Happy to read that Klila, thank you for your comment!
Nice information. What about someone wants to run the test against other browser agents (Like Firefox / Safari). Puppeteer only supports chrome.
Which IDE and plugins are you using for IntelliSense / Autocomplete and showing library function documentation?
This is my VS Code setup => academind.com/learn/web-dev/visual-studio-code-introduction/#our-visual-studio-code-setup
Wow! Great Job!! Thank you very much for this video. Looking forward to the next one
Thanks a lot for your awesome feedback Eduardo, this really means a lot to me!