Discussion on "A better approach for testing your Redux code"

Henrique Barcelos · 2019-11-25T22:50:44.000Z

TL;DR When testing Redux, here are a few guidelines: Vanilla Redux The smallest standalone unit in Redux is the entire state slice. Unit tests should interact with it as a whole. There is no point in testing reducers, action creators and selectors ...

Henrique Barcelos Very interesting and amazing article, you can update it using createAsyncThunk in v1.3.2 for async actions. But I have a simple question here: why are you adding the error as selector in the code and is it useful to do that?

I have heard of createAsyncThunk, but didn't have a chance to play with it yet. As soon as I got some spare time I'll do that. Thanks.

I use selectors for anything I might want to use in a component.

Sometimes I want to provide feedback to the user about an action that failed, even if I need to embellish it first. For that reason, I need to extract the error from the store, therefore the selector.

Nice read, thanks for sharing Henrique Barcelos. :)

Discussion

A better approach for testing your Redux code

Responses(2)

Recent in Forum

Search Hashnode

A better approach for testing your Redux code

Responses(2)

Recent in Forum