fix: hoist backend vitest mocks to module scope (@LekhanaMitta) - #8323
Open
LekhanaMitta wants to merge 1 commit into
Open
fix: hoist backend vitest mocks to module scope (@LekhanaMitta)#8323LekhanaMitta wants to merge 1 commit into
LekhanaMitta wants to merge 1 commit into
Conversation
fehmer
approved these changes
Aug 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes a backend test setup issue by hoisting the Vitest mock registrations to module scope.
The backend test files were calling
vi.mock(...)from helper/setup functions duringbeforeAll. Vitest hoistsvi.mockcalls, so placing them inside runtime setup can lead to incorrect module resolution order and unstable worker execution. I moved these mocks to the top level of the setup modules so they are registered in the expected order before the tests run.This keeps the backend test harness aligned with Vitest’s mock semantics and prevents the worker instability that was appearing during the backend integration run.
Verified with:
pnpm test-be
This passes after the change.