Expense Analyser Test Builder

3. Establish folder layout.

• Component tests: src/components/__tests__/*.spec.ts
• Store tests: src/stores/**/__tests__/*.spec.ts
• Service tests: src/services/__tests__/*.spec.ts
• Shared test utils: src/tests/*

4. Add first coverage in this order.

• Pure utilities/models with no Vue runtime dependency.
• Stores with mocked services.
• Components with store and router mocks.
• Service wrappers with mocked axios behavior.

5. Handle known project side effects.

• Mock TextractNotificationService.start/stop in tests that touch auth flow.
• Mock useNotificationStore when testing useAuthStore.login.
• Stub router pushes and route guards instead of running full navigation for unit tests.

6. Validate in CI-style order.

• Run npm run test.
• Run npm run test:coverage.
• Run npm run type-check.
• Run npm run lint.

Coverage Targets

Prioritize high-risk paths:

• Auth session transitions (login, checkSession, logout)
• Expense create/list/delete flows in store actions
• Notification rendering branches (friend request vs normal message)
• Error handling paths in services (axios.isAxiosError branches)

Guardrails

• Do not call real backend APIs in unit tests.
• Do not rely on shared mutable store state across tests; reset Pinia and mocks per test.
• Keep tests deterministic; avoid sleeps/timeouts unless testing retry/debounce logic.
• Add tests near the domain they cover to keep maintenance cost low.