test(web): dashboard alert drill-down source test expects stale expression #784

Open
opened 2026-06-26 15:56:54 +00:00 by simon · 0 comments
Owner

While validating the AI model settings work, the full web unit suite failed on an unrelated existing source-level test:\n\n- Command: find lib -name '*.test.mjs' -print0 | xargs -0 node --experimental-strip-types --test from apps/web\n- Failing test: lib/actions/dashboard-standalone.test.mjs -> dashboard alert drill-down tile shows only active alerts\n- Failure: expected the dashboard client source to match const hasActiveAlerts =\s*data.alerts.firing > 0, but the current source no longer contains that exact expression.\n\nThis appears unrelated to AI settings. The focused AI tests, mutation authz test, migration validation, direct TypeScript check, and production Next build all pass on the feature branch.\n\nSuggested fix: update either the dashboard implementation to restore the intended active-alert-only variable or update the source-level test to assert the current equivalent behavior.

While validating the AI model settings work, the full web unit suite failed on an unrelated existing source-level test:\n\n- Command: `find lib -name '*.test.mjs' -print0 | xargs -0 node --experimental-strip-types --test` from `apps/web`\n- Failing test: `lib/actions/dashboard-standalone.test.mjs` -> `dashboard alert drill-down tile shows only active alerts`\n- Failure: expected the dashboard client source to match `const hasActiveAlerts =\s*data.alerts.firing > 0`, but the current source no longer contains that exact expression.\n\nThis appears unrelated to AI settings. The focused AI tests, mutation authz test, migration validation, direct TypeScript check, and production Next build all pass on the feature branch.\n\nSuggested fix: update either the dashboard implementation to restore the intended active-alert-only variable or update the source-level test to assert the current equivalent behavior.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
carrtech/ct-ops#784
No description provided.