You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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',()=>{conststore=makeStore()// a user defined reusable store factorystore.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.
redux-mock-store
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.
Install
npm install redux-mock-store --save-dev
Or
yarn add redux-mock-store --dev
Usage
Synchronous actions
The 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.
importconfigureStorefrom'redux-mock-store'//ES6 modulesconst{ configureStore }=require('redux-mock-store')//CommonJSconstmiddlewares=[]constmockStore=configureStore(middlewares)// You would import the action from your codebase in a real scenarioconstaddTodo=()=>({type: 'ADD_TODO'})it('should dispatch action',()=>{// Initialize mockstore with empty stateconstinitialState={}conststore=mockStore(initialState)// Dispatch the actionstore.dispatch(addTodo())// Test if your store dispatched the expected actionsconstactions=store.getActions()constexpectedPayload={type: 'ADD_TODO'}expect(actions).toEqual([expectedPayload])})
Asynchronous actions
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.
importconfigureStorefrom'redux-mock-store'importthunkfrom'redux-thunk'constmiddlewares=[thunk]// add your middlewares like `redux-thunk`constmockStore=configureStore(middlewares)// You would import the action from your codebase in a real scenariofunctionsuccess(){return{type: 'FETCH_DATA_SUCCESS'}}functionfetchData(){return(dispatch)=>{returnfetch('/users.json')// Some async action with promise.then(()=>dispatch(success()))}}it('should execute fetch data',()=>{conststore=mockStore({})// Return the promisereturnstore.dispatch(fetchData()).then(()=>{constactions=store.getActions()expect(actions[0]).toEqual(success())})})
API
configureStore(middlewares?: Array)=>mockStore: Function
Configure mock store by applying the middlewares.
mockStore(getState?: Object,Function)=>store: Function
Returns 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)=>action
Dispatches an action through the mock store. The action will be stored in an array inside the instance and executed.
store.getState()=>state: Object
Returns the state of the mock store.
store.getActions()=>actions: Array
Returns the actions of the mock store.
store.clearActions()
Clears the stored actions.
store.subscribe(callback: Function)=>unsubscribe: Function