How do you test actions generated by a slice?

Q: How do you test actions generated by a slice?

Actions generated by `createSlice()` in Redux Toolkit can be easily tested since they are plain JavaScript objects. You can test them by calling the action creator and verifying that it returns the correct action type and payload. Import the auto-generated action creator from the slice file. Call the action creator with the desired payload. Check that the returned object matches the expected `type` and `payload` structure. import { addTodo } from './todosSlice'; test('addTodo action creator returns correct action', () => { const action = addTodo('Learn Redux Toolkit'); expect(action.type).toBe('todos/addTodo'); expect(action.payload.text).toBe('Learn Redux Toolkit'); expect(action.payload).toHaveProperty('id'); expect(action.payload).toHaveProperty('createdAt'); }); Since `createSlice()` automatically generates action creators, these functions can be tested like any other pure JavaScript function — without needing to mock the Redux store.

Difficulty: 5/10

slice actions, testing, RTK async thunks

Testing Actions Generated by createSlice in Redux Toolkit

Actions generated by createSlice() in Redux Toolkit can be easily tested since they are plain JavaScript objects. You can test them by calling the action creator and verifying that it returns the correct action type and payload.

Steps to Test Slice Actions

1
Import the auto-generated action creator from the slice file.
2
Call the action creator with the desired payload.
3
Check that the returned object matches the expected type and payload structure.

Example: Testing Slice Actions

Since createSlice() automatically generates action creators, these functions can be tested like any other pure JavaScript function — without needing to mock the Redux store.

Scenario Questions

0-2 years experience

1You have a Redux Toolkit slice with a simple synchronous reducer that increments a counter. How would you write a test to verify that dispatching the generated increment action updates the state as expected?
2If you run a unit test that calls the slice's action creator directly, what does the returned action object look like, and how can you assert its type and payload?

2-5 years experience

Follow-up Questions

Why did you choose that particular mocking technique for the thunk?
How would you test an action that triggers side‑effects outside Redux, like analytics calls?
What changes would you make to the test if the slice added extra middleware later?