Комментарии:
Amazing video. Many thanks for mocking example with axios.
Ответитьfor toBeCloseTo() assertion you can see the error not passed test, it show the limit (expected difference is 0.005)
ОтветитьСпасибо за новое видео. Уже давно слежу за вашим каналом, нашла много полезного для себя.
ОтветитьVery cool, thanks! I am starting to learn jest. Your course has been very helpful!
ОтветитьBeautiful video, crisp, to the point and nice explanation!
Ответитьthe course is really cool but the mocks part needed more explination and clarification
ОтветитьSuch a nice tutorial, you're amazing. Thank you!❤❤❤
ОтветитьReally nice
ОтветитьThere is an error on the jest home page at the beginning:
it says: "Jest is a delightful javascript testing framework".
It should be "Jest is shit and a nightmare".
Best Explanation Ever for Jest, Just Incredible
ОтветитьLaith, you do deserve a 1M Subs for sure!
Thanks for the content.
Thanks. Wish you went more into mocking with classes and stuff.. but I get it now. ❤
Ответитьgreat lecture... keep it up
ОтветитьThanks Laith, liked the course! Would've preferred a few less matcher methods and a bit more advanced info though, like using Jest with ES modules or testing React.
ОтветитьNice course, very informative I have learned a lot.
Thank You ❤️
I see you're a fan of Traversy Media lol gotta practise that Boston accent to really stick the landing 😜
ОтветитьFor anyone who struggled to understand how the mock.calls worked, as I did, too, initially - here is what [x] [y] mean: x represents the index of the call made (i.e. 0 = first call, 1 = second call, 2 = third call etc) and y represents the index of the first argument we find on that call (i.e. always 0 as we only have one argument).
So, taking our example in the tutorial 'expect(mockCallback.mock.calls[1][0]).toBe(1)' - [1] represents the second call and [0] first argument, which in this case is 1. Hope this helps to clarify and keep up the good work studying!
Thanks Laith Academy! <3
Can you please tell me how to write unit test for a button click..
Ответитьthank you
ОтветитьVery good and helpful crash course👍👍👍
ОтветитьI love your contest Laith! Been following your content when you had only few hundred subscribers : ) Do you have any plan to make web3 development tutorials in future?
ОтветитьThank you sir
ОтветитьDoes it include api and database mocking
ОтветитьReal nice tutorial L. Thanks for your hard work. 🙂
ОтветитьThis channel is incredible, your teaching skill is great. Thank you, I appreciate what you're doing on this channel.
ОтветитьYou are the GOAT thanks a lot!
ОтветитьNot sure if mentioned but I believe a mocked module/function must be included/required in the test code.
ОтветитьGreat stuff, thanks for this!
Ответитьcool thing. nice explanation
ОтветитьNice! Especially thanks for mocking example with axios
ОтветитьThank you so much. since long I was not able to get understanding of mocking which you explained practically in good way.. thanks and keep on.
ОтветитьIt's a bad practice and something to avoid when testing real endpoints. You should have a mock data, preferably using MSW package to mock your endpoints. Never test real endpoints.
ОтветитьNice course but I didn't get mocks
ОтветитьVery helpful video! Thank you!
ОтветитьLaith, very good tutorial on Jest. Do you have any tutorial on JEST with LWC component to test field value on clicking submit button in the LWC.
ОтветитьThanks Laith
ОтветитьPlease a video for testing next.js with typescript
ОтветитьAre you Brad? :)
ОтветитьNice tutorial 👍
Ответитьthank you for this
ОтветитьGreat course, thanks for including mocks and not just the simple pure function stuff.
ОтветитьThank you .
The mocks part in the tutorial needs to be demystified more.
Thanks for providing Jest & React testing Library courses 🙏
ОтветитьI have to say, you have the best quality tutorials out there!
Ответитьwow you create the video in one shot, that is amazing
Ответить