I like entire course, not because framework but because we have situation like "oh this was unexpected", "it should work". It feels real and not like idealized presentation.

I just want to thank you for acknowledging when something doesn't go right and you do a quick troubleshoot of it. I think it's important for newer developers to see that things often don't go as we expect no matter how much experience you have.

To be honest i was a little sceptical about this course, because shawn was not the host, but it turns out really good

I tried few Unit testing tutorials and i only get hooked by this one. Comment for algorithm, nice1. I checked your website For extensive Unit testing course but i haven´t found one. I would be up for it with this instructor, Testing some large application while developing features, or sth like this

I got to say, at first I was intimidated by the idea of Testing my Code, but after seeing this series, it really isn't that hard after all.

You’re all doing the Lord’s work.

First heeeeeere!!! 6:26 am from brazil

Loved this course.. great job man!!!

Amazing videos!~Watching on 1.5x speed, but great!

Better and more safe - use instead of fireEvent - userEvent

Thats why he is the GOAT!! The GOATTT!

More technically speaking, if both of your components are running in the same service, and you are testing their cooperation, then this is a "narrow integration" test. In case if these 2 units of functionalities are in separate autonomous services this can be now called an "integration" test. Please correct me if I am wrong.

aha Second !. Thank u Sir. When will u start react native app Testing tutorial

thanks laith n shaun.

I am curious why you are using regular expressions over just a string. Is it better in terms of something?

Why was I not able to find this easy work around to on the RTL docs? I feel like there's so much missing from it.

I watch at 2x but thats how I watch most of the videos, so dont waste time. Laith and Shawn are awesome instuctors ;)

At 15:15 we can check for multiple todo items at once: it('should not have todo-item-active class for a todo-item initially', () => { render(); // We're adding 4 tasks via addTask() addTask(["Go to Store", "Go to Gym", "Do Yoga", "Code all day long"]) const todoItemElements = screen.getAllByTestId('todo-item'); todoItemElements.forEach(todoItemElement => { expect(todoItemElement).not.toHaveClass('todo-item-active'); }) });

very helpful, thank you!

why are the `it` blocks inside describe async? we are not using any find methods right

Wonderful content! I learned a lot with the course, thanks a lot for this and great job!

isn't it better if the last test you put there has a separate unit test specifically for the TodoList component?

NICE!!

is very good. Thanks for your very good tutorial 😍

Does anyone here know what he is using to make is so when he clicks a component, it takes you right into that folder. It would save me a lot of time. Thanks Edited :He explained it in the video. You simply press Ctrl and click it. It is an incredibly handy trick.

Great content. Please, in the course of following the tutorial, I noticed my tests stopped giving me any output and my VS Code kept flickering. I guess there is a memory leakage or issue somewhere as it runs indefinitely with no progress. Any idea on how I can resolve this?

Thank you

Great course! Quick question - usually when I write tests I just use 'strings' to identify elements and check values, placeholders, etc. What are the advantages of using regular expressions instead?

i did one diferent test and for one hour i has stocking because give me one error, than i check the code and realize the test is ok the code is wrong ...

This one is so clear but one doubt is if that text actually brings some array of data asynchronously through api then how to wait for to complete??

Washing hands is really important, because of COVID! 😁 Sadly it is true! 😞

Thanks!

Man !! this a awesome great video tutorial series, but i have a question ..if i have for example a E-comerce website with 3 pages: products list, product details and a shopping cart page , and i would do 1 integration test for each page ?...im trying figure this out 🤔 thankx 👍

Replace forEach loop with for..of loop if you are using an asynchronous userEvent() instead of fireEvent(). And await the addTask function like shown below const addTask = async (tasks) => { const inputElement = screen.getByPlaceholderText(/Add a new task here.../i); const buttonElement = screen.getByRole("button", { name: /Add/i }); const user = userEvent.setup(); for (const task of tasks) { await user.type(inputElement, task); await user.click(buttonElement); } }; .... await addTask(["Go Grocery Shopping", "Wash Hands", "Clean pet"]); .....

Why don't you just pause the video making for some time and " Go Grocery Shopping" once. This is something in your Todos since years now.😏

wash your hands bro 🤣

Why are you testing for class presence? Why should user care whether some divs in source code have a specific class? I don't know much about testing (that's why I'm watching this), but I have a feeling that this is a crap tutorial.