How to test Redux-connected React components
Hey there 👋
This week I have one new article and one UI/UX update from my blog.
I gave my blog a small facelift that includes a new footer and landing page.
Previously, I would have the blue newsletter signup tile next to every blog post in the sidebar. Since this was a bit too distracting from my content, I moved it into the footer where it still has enough visibility. Time will tell if this will affect newsletter signups, but I prefer it this way since it’s less intrusive.
You can now see my most popular posts next to my latest ones on the landing page, which will hopefully entice visitors to browse my website a bit more.
I am thinking of adding search to it, although I’ll probably be one of the main users of that feature.
What do you think about that minor redesign? What would you add or change? Suggestions are more than welcome!
If you want to learn web development through online courses, you can currently get a 1-month premium membership of SkillShare with this link for free (cancel any time).
I also have a course published there in case you want to learn more about Progressive Web Apps 😉
Again, I was running into this question a few weeks ago. What’s the best way to test Redux-connected components? Should I mock the store or not?
After trying to mock the store effectively, I read a few of Kent C. Dodds’s articles, which made me realize that the best way to test my components is by not mocking the store at all.
In the article, I walk you through the process of creating tests with a Redux store and why mocking the store isn’t a good idea.
The solution is surprisingly clean and straightforward, so I plan on going this route for now. If I change my mind on this topic in the future, I’ll revisit the article, but it seems like the best approach until then.
Those are all the updates I have for you this week.
Thanks for reading, and have a great week!