gsadmin/pulse
1
0
Fork 0
mirror of https://github.com/rcourtman/Pulse.git synced 2026-10-15 16:42:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

test(frontend): repin patrol findings badge boundary to getPatrolWorkspaceWorkGroups

Browse Source 
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.
This commit is contained in:
rcourtman
2026-07-17 14:17:48 +01:00
parent c4433edadf
commit 8830eb66b7
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
frontend-modern/src/utils/__tests__/frontendResourceTypeBoundaries.test.ts
+5 -4
View File
@@ -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',
);