From 8830eb66b745acb66032efbe40981629a5a99876 Mon Sep 17 00:00:00 2001 From: rcourtman Date: Fri, 17 Jul 2026 14:17:48 +0100 Subject: [PATCH] test(frontend): repin patrol findings badge boundary to getPatrolWorkspaceWorkGroups The open-work-queue redesign removed findingsBadgePresentation from PatrolIntelligenceWorkspace; work-group badge tones now resolve in patrolControlPresentation and render as tone={group.tone} on MetadataBadge. Repin the boundary assertion to that canonical location. --- .../__tests__/frontendResourceTypeBoundaries.test.ts | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/frontend-modern/src/utils/__tests__/frontendResourceTypeBoundaries.test.ts b/frontend-modern/src/utils/__tests__/frontendResourceTypeBoundaries.test.ts index 9d6fb5a9d8..b4b797b02e 100644 --- a/frontend-modern/src/utils/__tests__/frontendResourceTypeBoundaries.test.ts +++ b/frontend-modern/src/utils/__tests__/frontendResourceTypeBoundaries.test.ts @@ -3576,10 +3576,11 @@ describe('frontend resource type boundaries', () => { expect(patrolSummaryPresentationSource).toContain('badgeVariant:'); expect(patrolSummaryPresentationSource).not.toContain('badgeClass:'); expect(patrolIntelligenceWorkspaceSource).toContain('MetadataBadge'); - expect(patrolIntelligenceWorkspaceSource).toContain('findingsBadgePresentation().tone'); - expect(patrolIntelligenceWorkspaceSource).not.toContain( - 'findingsBadgePresentation().toneClasses', - ); + // Work-group badge tones resolve in the patrolControlPresentation adapter + // (getPatrolWorkspaceWorkGroups), never inline in the workspace component. + expect(patrolIntelligenceWorkspaceSource).toContain('getPatrolWorkspaceWorkGroups'); + expect(patrolIntelligenceWorkspaceSource).toContain('tone={group.tone}'); + expect(patrolIntelligenceWorkspaceSource).not.toContain('findingsBadgePresentation'); expect(patrolIntelligenceWorkspaceSource).not.toContain( 'ml-1.5 px-1.5 py-0.5 text-xs rounded-full', );