frontend-unit-testing

To write Vitest tests for React components, use project utilities like ConfigWrapper or createConfigWrapper for rendering, and userEvent.setup() for interactions, ensuring tests align with repository standards.

The best way to mock API requests in frontend unit testing is using MSW (Mock Service Worker), which intercepts network requests to provide controlled response data for your component and route tests.

To test React hooks with Vitest, use the renderHook utility combined with project-specific wrappers like createTestContext and ConfigWrapper to provide necessary providers and context to your hooks.

No, you should avoid direct imports from vitest globals. Instead, follow project conventions by using the provided test utilities and wrappers to maintain consistent testing patterns across the repository.

To test route and server actions under the frontend directory, utilize createTestContext and createFormDataRequest utilities alongside MSW for mocking, ensuring proper coverage of interactions and providers.

Yes, this approach works for testing React providers and context by leveraging createTestContext and ConfigWrapper, which allow you to wrap components with necessary providers during rendering and hook tests.