Context

The frontend has 1496 passing unit tests across 134 files, but several views and critical components lack any test coverage. As the app grows, these untested surfaces become blind spots for regression.

Untested or Under-Tested Views

Views With No Tests

• ArchiveView — archive listing, restore actions, empty state
• WorkspaceSettingsView (if exists) — settings management
• MetricsView — dashboard charts, date picker, board selector, loading/error/empty states

Views With Minimal Tests

• BoardView — the most complex view; drag-drop, column management, card CRUD, keyboard shortcuts, context menus. Board components have some tests, but the view orchestration is under-tested.
• ReviewView — proposal listing, approval/rejection actions, detail expansion
• ChatView (or chat panel) — message input, response display, tool-status indicators, degraded state
• InboxView — capture list, triage status, action buttons

Untested Critical Components

Board Components

1. Column drag-and-drop ordering — verify column positions update correctly
2. Card drag between columns — verify card moves to target column at correct position
3. WIP limit enforcement — column at WIP limit shows visual indicator, prevents adding more cards (or shows warning)
4. Card context menu — right-click/menu actions (edit, move, archive, delete, assign label)
5. Board header — board name editing, archive button, share button

Capture Components

6. Capture input — text input, submit button, keyboard shortcut (capture should feel fast)
7. Capture queue status indicator — shows triage progress

Review Components

8. Proposal card — operation summary, risk indicators, approve/reject buttons, detail toggle
9. Proposal detail panel — operation list, provenance links, diff view

Navigation

10. Sidebar — board list, active board highlight, workspace mode indicator
11. Router guards — unauthenticated user redirected to login, authenticated user redirected from login to home

Notifications

12. Notification bell — unread count badge, dropdown list, mark-as-read

Shared Components

13. Loading states — skeleton loaders, spinners across views
14. Empty states — "no boards yet", "no captures yet", "no proposals" — with clear CTAs
15. Error boundaries — component error does not crash entire app

Implementation Notes

• Use `@vue/test-utils` with `mount`/`shallowMount`
• Mock stores using `createTestingPinia` with initial state
• For drag-and-drop: test the event handlers and state changes, not the actual drag behavior (that's E2E territory)
• For router guards: use `@vue/test-utils` router mock or test the guard functions directly
• Focus on behavior over implementation: what does the user see/experience?

Priority Order

1. BoardView components (highest complexity, most used)
2. ReviewView + proposal components (core trust mechanism)
3. CaptureView + capture components (core input mechanism)
4. Navigation/router guards (security boundary)
5. Everything else