Goal#

Write unit tests for the 5 components with the lowest coverage (<30%):

1. SpendDashboard.tsx (2.4%) — cost/spend visualization, budget tracking UI. Mock cost data and render in various states.
2. TasksClient.tsx (17.9%) — main task list UI, filtering, sorting, pagination. High business value.
3. CapabilityAssignmentView.tsx (29.5%) — strategy capability routing UI, toggle save logic.
4. HardwareClient.tsx (29.0%) — hardware monitoring dashboard chart rendering.
5. CreateFixTaskModal.tsx (18.8%) — crash/hotfix task creation modal.

Requires: React Testing Library, DOM mocking for charts (recharts/Recharts). @testing-library/react is installed.

Acceptance#

• Each component has a test file: __tests__/<Component>.test.tsx
• Tests cover: render (loading, empty, error, data states), user interactions (button clicks, saves, toggles), edge cases (null/missing data, API failures)
• No regression — existing tests still pass
• @area annotation: "Test Coverage"

Tags#

[react-testing, coverage, <30pct]

Maxime's Answer#

Please reprocess this

Unblock Note (auto-bulk t-3551)#

Unblocked by mass-fix on 2026-05-12 because the 3-failure deadlock logic was buggy:

• It counted gateway-outage failures (ECONNREFUSED) as task failures
• It re-blocked tasks immediately after a manual status reset
• It ignored reviewState=approved

Failure baseline set to NOW. Only failures after this timestamp count toward the next 3-strike trigger. Infra failures (ECONNREFUSED, gateway OOM) are now excluded permanently.