Add render test helper to follow suggested Redux testing practices

[zetter-rpf]

In our tests we have a lot of boilerplate to set up redux state and providers in order to render components.

Redux suggests adding a renderWithProviders helper to manage this and make testing easier. See https://redux.js.org/usage/writing-tests

These changes add a renderWithProviders helper and changes a spec to use it.

If we're happy with this approach we can gradually move our existing tests over as we work on them.

One thing I wasn't sure about was naming of the helper and props - I've followed the example from redux, but it might be simpler and fit in with our existing code better if we call it render and initialState than preloadedState (however render will need to be renamed when imported if we want to mix styles in single test file).

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[Copilot]

Pull request overview

Adds a shared renderWithProviders test helper to reduce Redux boilerplate in component tests, and migrates SaveButton tests to use a real RTK store instead of redux-mock-store.

Changes:

• Introduce src/utils/renderWithProviders.js to create/configure a Redux store and wrap renders with react-redux’s <Provider>.
• Update SaveButton.test.js to use the new helper and assert state changes via the real reducer/store.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
src/utils/renderWithProviders.js	New RTL helper to render UI with a configured RTK store + Redux provider.
src/components/SaveButton/SaveButton.test.js	Refactors tests to use renderWithProviders and validate save behavior against real store state.

Comments suppressed due to low confidence (1)

src/components/SaveButton/SaveButton.test.js:11

• logInHandler is shared across all tests in this file and is never reset, so later assertions like expect(logInHandler).toHaveBeenCalled() can pass due to calls from earlier tests rather than the click under test. Clear the mock in a beforeEach/afterEach (or assert toHaveBeenCalledTimes(1) after clearing) to make these event tests independent and reliable.

const logInHandler = jest.fn();

describe("When project is loaded", () => {
  beforeAll(() => {
    document.addEventListener("editor-logIn", logInHandler);
  });

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[zetter-rpf]

In the redux example, it set up the apps root store instead of using configure store.

I want to look at this again to see if we can follow that pattern - this would mean that tests would use the same initial store as the app which might mean less setup