testing

Vitest testing guide for LobeHub with commands, patterns, and best practices. 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: - Run specific test files with bunx vitest run commands; avoid bun run test which runs 3000+ tests (~10 minutes) - Prefer vi.spyOn over vi.mock for targeted, maintainable mocks; use vi.stubGlobal for browser APIs - Test observable behavior rather than implementation details; delete param-forwarding tests that duplicate higher-level coverage - Includes detailed guides for database models, Electron IPC, Zustand stores, agent runtime E2E, and desktop controllers - Tests must pass type check; use beforeEach / afterEach for mock cleanup and state isolation - 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 :...