veta-testing

Write reliable Vitest tests by mocking Supabase and auth boundaries using provided helpers like mockSupabase and createMockSession, while using React Testing Library to validate UI behavior and server route logic.

The recommended test coverage target for new code is at least 85 percent. Reviewing coverage reports helps identify untested branches and ensures edge cases like empty states, invalid inputs, and Supabase error paths are verified for resilience.

Mock Supabase authentication boundaries in an integration test by importing boundary-focused helpers from the test mocks file, such as createMockUser, createMockSession, and mockSupabaseAuth, to isolate and control auth responses during UI flow verification.

Yes, this setup uses Vitest as the runner and React Testing Library for UI behavior testing. It targets key integration flows like adding budget items and creating projects, while explicitly avoiding testing framework internals or third-party library behavior.

When testing form validation and error paths, include edge cases such as empty states, invalid inputs, and Supabase error returns. Verifying both form validation success and failure scenarios ensures true resilience against regressions and brittle changes.

Full-stack test coverage hides real bugs when tests avoid error paths or fail to mock boundaries correctly. Applying Vitest with boundary-focused mocks for Supabase and auth ensures both UI flows and server route behavior are reliably verified against regressions.