13. How do you test thunks and async actions?

Testing Thunks and Async Actions in Redux Toolkit

Testing thunks and async actions in Redux Toolkit focuses on verifying that they dispatch the correct actions and handle asynchronous logic properly. You can test them in isolation without rendering components by mocking API calls and the Redux store.

Common Ways to Test Thunks

1
1. Mock API Calls: Use libraries like jest.fn() or msw to mock fetch or axios responses.
2
2. Assert Dispatch Calls: Verify that your thunk dispatches the expected pending, fulfilled, or rejected actions.
3
3. Use Mock Store: Create a fake Redux store using @reduxjs/toolkit’s configureStore or libraries like redux-mock-store for isolated testing.
4
4. Test Logic in Isolation: Call the thunk’s payload creator directly with mocked dispatch and getState to test business logic independently.

Example: Testing an Async Thunk with Jest

By mocking network requests and asserting dispatched actions, you can ensure that your thunks handle asynchronous behavior and side effects correctly without needing a real API or browser environment.

Difficulty: 6/10

Topics: thunk testing, mocking async calls, RTK testing utilities

Scenario Questions

0-2 years experience

1
You need to write a unit test for a thunk that fetches a list of users and stores them in the Redux store. Walk me through how you'd set up the test using RTK's testing utilities.
2
If the API call inside your thunk fails with a 500 error, what would you assert in your test to ensure the error handling path works?

2-5 years experience

1
We have a feature where a thunk dispatches multiple actions based on the response shape. In a recent bug, the success action wasn't being dispatched. How would you debug the test to pinpoint why?
2
When testing a thunk that uses a third‑party library for caching, what trade‑offs do you consider between mocking the library versus using the real implementation in your test suite?

5-8 years experience

1
Our application runs thousands of concurrent async thunks for real‑time updates. How would you design a testing strategy that catches race conditions and ensures state consistency without slowing CI pipelines?
2
Explain how you would mock the Redux store and middleware to test a thunk that depends on custom middleware that adds request IDs, and discuss the impact on test reliability.

8+ years experience

1
We are migrating a legacy codebase that uses hand‑rolled async action creators to RTK thunks across multiple teams. What guidelines would you establish for testing to keep the migration safe and maintainable at scale?
2
How would you set up a shared testing framework for thunks that enforces consistent mocking of API clients, handles versioned endpoints, and integrates with contract testing across services?

Follow-up Questions

❓What advantage does using Redux Toolkit's built‑in mockStore give you over a hand‑rolled mock?
❓How do you ensure your async tests don’t cause false positives due to unawaited promises?
❓Can you explain how you’d test cancellation logic in a thunk that uses AbortController?