A mock store for testing Redux async action creators and middleware.
A mock store for testing Redux async action creators and middleware.
The Redux team does not recommend testing using this library. Instead, see our docs for recommended practices, using a real store.
Testing with a mock store leads to potentially confusing behaviour, such as state not updating when actions are dispatched. Additionally, it's a lot less useful to assert on the actions dispatched rather than the observable state changes.
You can test the entire combination of action creators, reducers, and selectors in a single test, for example:
it('should add a todo', () => {
const store = makeStore() // a user defined reusable store factory
store.dispatch(addTodo('Use Redux'))
expect(selectTodos(store.getState())).toEqual([
{ text: 'Use Redux', completed: false }
])
})This avoids common pitfalls of testing each of these in isolation, such as mocked state shape becoming out of sync with the actual application.
A mock store for testing Redux async action creators and middleware. The mock store will create an array of dispatched actions which serve as an action log for tests.
Please note that this library is designed to test the action-related logic, not the reducer-related one. In other words, it does not update the Redux store. If you want a complex test combining actions and reducers together, take a look at other libraries (e.g., redux-actions-assertions). Refer to issue #71 for more details.
npm install redux-mock-store --save-devOr
yarn add redux-mock-store --devThe simplest usecase is for synchronous actions. In this example, we will test if the addTodo action returns the right payload. redux-mock-store saves all the dispatched actions inside the store instance. You can get all the actions by calling store.getActions(). Finally, you can use any assertion library to test the payload.
…A common usecase for an asynchronous action is a HTTP request to a server. In order to test those types of actions, you will need to call store.getActions() at the end of the request.
…configureStore(middlewares?: Array) => mockStore: FunctionConfigure mock store by applying the middlewares.
mockStore(getState?: Object,Function) => store: FunctionReturns an instance of the configured mock store. If you want to reset your store after every test, you should call this function.
store.dispatch(action) => actionDispatches an action through the mock store. The action will be stored in an array inside the instance and executed.
store.getState() => state: ObjectReturns the state of the mock store.
store.getActions() => actions: ArrayReturns the actions of the mock store.
store.clearActions()Clears the stored actions.
store.subscribe(callback: Function) => unsubscribe: FunctionSubscribe to the store.
store.replaceReducer(nextReducer: Function)Follows the Redux API.
< 1.x.x)https://github.com/arnaudbenard/redux-mock-store/blob/v0.0.6/README.md
The following versions are exposed by redux-mock-store from the package.json:
main: commonJS Versionmodule/js:next: ES Module Versionbrowser : UMD versionThe MIT License
No open issues yet, or sync has not completed.