This post is part one of aseries, covering techniques for testing redux reducers. One of the benefits of using redux is the ease of testing. Keeping state management separate from the rest of our application makes it easier to test in isolation. That said, the mechanics of testing the various moving parts in a redux app - stores, reducers, actions, action creators, selectors - is not entirely obvious. One question that I see crop up frequently is how granular our tests should be. Should we te...
