🐛 168 test failure(s) in Coverage Suite run #3903

[clubanderson]

Test Failures Detected

168 test(s) failed in the Coverage Suite run #3903.

Triggered by

• Commit: 4435c9c

• Author: clubanderson

• PR: #19652 — [quality] add unit tests for analytics-accm helpers, pipelines helpers, and layout utils by @kubestellar-hive[bot]

Failing tests (168)

• src/components/cards/backstage_status/backstage_status.test.tsx > BackstageStatus renders skeleton when loading
• src/components/cards/backstage_status/backstage_status.test.tsx > BackstageStatus renders without error when data is loaded
• src/components/cards/grpc_status/grpc_status.test.tsx > GrpcStatus renders skeleton when loading
• src/components/cards/grpc_status/grpc_status.test.tsx > GrpcStatus renders without error when data is loaded
• src/components/cards/linkerd_status/linkerd_status.test.tsx > LinkerdStatus renders skeleton when loading
• src/components/cards/linkerd_status/linkerd_status.test.tsx > LinkerdStatus renders without error when data is loaded
• src/components/cards/rook_status/rook_status.test.tsx > RookStatus renders skeleton when loading
• src/components/cards/rook_status/rook_status.test.tsx > RookStatus renders without error when data is loaded
• src/components/cards/spiffe_status/spiffe_status.test.tsx > SpiffeStatus renders skeleton when loading
• src/components/cards/spiffe_status/spiffe_status.test.tsx > SpiffeStatus renders without error when data is loaded
• src/components/missions/MissionBrowser.components.test.tsx > MissionBrowserFilterPanel renders without errors
• src/components/missions/MissionBrowser.components.test.tsx > MissionBrowserFixesTab renders without errors
• src/components/missions/MissionBrowser.components.test.tsx > MissionBrowserInstallersTab renders without errors
• src/components/missions/MissionBrowser.components.test.tsx > MissionBrowserRecommendedTab renders without errors
• src/components/missions/MissionBrowser.components.test.tsx > MissionContentContext exports useMissionContent hook
• src/components/missions/MissionBrowser.test.tsx > MissionBrowser does not render when closed
• src/components/missions/MissionBrowser.test.tsx > MissionBrowser renders without errors
• src/components/missions/MissionDialogs.test.tsx > ConfirmMissionPromptDialog renders without errors
• src/components/missions/MissionDialogs.test.tsx > ImproveMissionDialog renders without errors
• src/components/missions/MissionDialogs.test.tsx > SaveResolutionDialog renders without errors
• src/components/missions/MissionDialogs.test.tsx > ShareMissionDialog renders without errors
• src/components/missions/MissionDialogs.test.tsx > StandaloneOrbitDialog renders without errors
• src/components/missions/MissionDialogs.test.tsx > SubmitToKBDialog renders without errors
• src/components/missions/MissionTypeExplainer.test.tsx > MissionTypeExplainer does not render in non-demo mode
• src/components/missions/MissionViews.test.tsx > MissionContentViewer renders without errors
• src/components/missions/MissionViews.test.tsx > MissionLandingPage renders without errors
• src/components/missions/MissionViews.test.tsx > OrbitStatusTracker renders without errors
• src/components/missions/MissionViews.test.tsx > ResolutionHistoryPanel renders without errors
• src/components/missions/MissionViews.test.tsx > ResolutionKnowledgePanel renders without errors
• src/components/missions/__tests__/PreflightFailure.test.tsx (failed to load)
• _...and 138 more_

Coverage was merged. Badge update was skipped due to a test shard failure.

Action needed

1. For each failing test, determine if it's a test update needed or a potential regression
2. Fix and close this issue

Auto-generated by Coverage Suite workflow

[github-actions]

🐝 Hi @clubanderson! I'm kubestellar-hive[bot], an automation bot for this repo.

Trusted users — org members and contributors with write access — can mention @kubestellar-hive in a comment to trigger repo automation.
On issues, that mention queues an automated fix attempt. On pull requests, it records extra context for existing automation.
This is not an interactive Q&A bot, so mentions should be treated as requests for automation rather than a conversation.

Automation may take a moment to start, and follow-up happens through workflow activity rather than chat replies.

[clubanderson]

Fixed by #19663 which was merged as commit 9234498. The root cause was IntersectionObserver/ResizeObserver mocks in web/src/test/setup.ts running unconditionally in Node.js environment, corrupting the global scope for subsequent jsdom tests in CI.