I’ve found it preferable to simply use a mockServiceCreator function with a suite of body fixtures. You can also use fetch-mock to mock the HTTP requests, but that might be overkill. If needed, you can apply the middleware to said store using redux-mock-store. So unit tests should only know about actions/events and state.įor async action creators using Redux Thunk (or other middleware), mock the (minimally) required Redux store for testing. Actions & Async Action CreatorsĪll we care about here is that the correct action creator was called and it returned the right action.
This article assumes you are already happy and comfortable using React, Redux, and know the basic testing methods from Enzyme. What follows is a comprehensive set of best practices I’ve identified for circumspect React/Redux Unit Testing. I’ve become a huge fan and promoter of the practice, which has led me to examine and identify strategies to avoid interdependence, support common set-up and teardown logic, and bypass mucking about with implementation details.
My work on a recent project has followed a very by-the-book Test-Driven Development (TDD) approach.
0 kommentar(er)
