React Testing Library Tutorial #8 - Assertions

preview_player
Показать описание
Check out Laith's YouTube channel for more tutorials:

🐱‍💻 Access the course files on GitHub:

🐱‍👤 Get access to extra premium courses on Net Ninja Pro:

🐱‍💻 Full React Course:

🐱‍💻 Social Links:
Рекомендации по теме
Комментарии
Автор

I'm loving this course, testing is one important thing that most of job openings require and most courses don't cover it

brnheavymetal
Автор

render(<TodoFooter numberOfIncompleteTasks={1}/>, {wrapper:BrowserRouter}); use wrapper option for BrowserRouter instead of creating mock component.

pawankotak
Автор

You're literally a lifesaver. Needed to learn testing quick for an interview assignment, like always, yours is the perfect playlist. Couldn't find a storybook playlist from you so dropping in a comment to suggest you to make one for the same.

sky_kryst
Автор

This is so well explained and I appreciate the hard work in putting this series together. I feel more confident with using RTL now. I am just waiting for the asynchronous testing section.

SimPwear
Автор

At 13:30 one can add role="paragraph" to p tag and test will work.

akash-kumar
Автор

I like the way you not skip the error and showing to us how to fixed it, even if its just a little error there always be lesson to learn

rizqyhbb
Автор

Very very well explained. I have always loved the way Laith explains the concepts. Stays in my mind forever.

programmed
Автор

Awesome and detailed explanation with examples makes it a great course. Thanks for the author. ❤

maheshr
Автор

great videos net ninja, i have a question,
is it better just having[componentname].test.js on same directory level of that component, or move everything under __test__ folder? why yes/not?

rickvian
Автор

I keep getting this error: "Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports."

TodoFooter is imported and MockTodoFooter is being used. I'm basically just using what is in the 03-Assertions tutorial branch

MinisterGold
Автор

Creating some proxy component to reuse in several tests is interesting

vasiliyandreychikov
Автор

Thank you!! Really this channel is Amazing!!

amershboul
Автор

is it correct to say pElement is : <p>1 task left</p>  ? plz answer

helia
Автор

what a nice tutorial! thank you so much!

racmathafidz
Автор

Can I get some problem when I am using async whithout an await?

gabrielmedeiros
Автор

Hello Boss, any tut for testing server side code? express, mongoose...

NinjaJutsu-yd
Автор

GOD BLESS YOU SIR..
THE BEST BEST BEST TRAINER :)

vinayaksonar
Автор

Hi Can you please upload video for react test coverage.

dhanabalt
Автор

Sup bruh. Please, in the next tutorial can you teach us how to implement stripe payments?! I really can't find any helpful tutorials

JMuks
Автор

It looks like some kind of nonsense =) I don't understand why to write all this, if it's already clear that the component is working, the application is working, and so on). It's just visible with the eyes and actions that you can check everything with - using the application. And so it turns out, you write a test for half an hour to see obvious things, for example, what the header has... The motivation to watch without this knowledge is completely lost... There are no special complaints about the submission and lessons, thanks for the work.

NeoCoding