test-frontend-unit

Frontend hook tests validate custom hooks or composables by testing state logic and effects in isolation. This generates framework-agnostic hook test suites that mock external dependencies and assert state transitions.

Vitest is the primary test runner for frontend unit testing, while Jest is supported if the project already uses it. Both runners integrate with @testing-library to execute component and hook tests.

Mocking API clients and external modules isolates components and hooks from backend dependencies during frontend unit testing. This provides mock implementations and spies to assert interaction behavior without real network calls.

Client-side routing and state store tests are covered to verify navigation flows and state mutations across frameworks. This produces test patterns that assert store state changes and route transitions accurately.

Avoid frontend unit testing for backend unit tests, E2E/UI tests, or Playwright BDD scenarios. Use it exclusively for component, hook, store, and utility tests on the client side.