test

Run Vitest unit tests by calling real `src/api/*` functions directly with a fresh in-memory SQLite database per test, avoiding mocks or hand-rolled SQL. This ensures API-layer correctness and deterministic database state validation for each test case.

Verify Vue modal and router changes by performing additional manual or MCP UI verification steps. This catches visual correctness and rendering gaps that automated component tests and Playwright e2e tiers cannot fully observe across the rendering stack.

Playwright e2e testing works with the packaged Tauri binary by running end-to-end tests against the compiled application. This CI gating tier captures regression evidence and validates the full application stack before merging changes.

Enforce ESLint and test coverage thresholds by running lint with zero errors first, then executing the full test suite. This quality gate prevents broken changes by blocking commits that fail static analysis or insufficient test coverage requirements.

Database import tests fail because regression-proof assertions require checking database state directly for import and transform correctness. Column-name bugs in event placement can bypass API assertions, so direct SQLite state verification is necessary to catch them.

You cannot use mocks, IPC calls, or Vue components in unit tests. The API-first test discipline requires calling actual `src/api/*` functions with per-test SQLite isolation to ensure deterministic execution and true API-layer correctness validation.