testing

Commands: Never run bun run test - it runs all 3000+ tests (~10 minutes). See references/ for specific testing scenarios: When tests fail due to implementation changes (not bugs), evaluate before blindly fixing: - Prefer vi.spyOn over vi.mock - More targeted, easier to maintain - Tests must pass type check - Run bun run type-check after writing tests - After 1-2 failed fix attempts, stop and ask for help - Test behavior, not implementation details - Database Model testing : references/db-model-test.md - Electron IPC testing : references/electron-ipc-test.md - Zustand Store Action testing : references/zustand-store-action-test.md - Agent Runtime E2E testing : references/agent-runtime-e2e.md - Desktop Controller testing : references/desktop-controller-test.md - Behavior tests : Tests that verify what the code does (output, side effects, user-visible behavior). Just update mock data formats or expected values. - Example: Tool data structure changed from { name } to { function: { name } } → update mock data - Example: Output format changed from Current date: YYYY-MM-DD to Current date: YYYY-MM-DD (TZ) → update expected string - Param-forwarding tests : Tests that assert exact internal function call arguments (e.g., expect(internalFn).toHaveBeenCalledWith(expect.objectContaining({ exact params })) ) — these break on every refactor and duplicate what behavior tests already cover. -...