## Summary - introduce a shared operator outcome taxonomy with semantic axes, severity bands, and next-action policy - apply the taxonomy to operations, evidence/review completeness, baseline semantics, and restore semantics - harden badge rendering, tenant-safe filtering/search behavior, and operator-facing summary/notification wording - add the spec kit artifacts, reference documentation, and regression coverage for diagnostic-vs-primary state handling ## Testing - focused Pest coverage for taxonomy registry and badge guardrails - operations presentation and notification tests - evidence, baseline, restore, and tenant-scope regression tests ## Notes - Livewire v4.0+ compliance is preserved in the existing Filament v5 stack - panel provider registration remains unchanged in bootstrap/providers.php - no new globally searchable resource was added; adopted resources remain tenant-safe and out of global search where required - no new destructive action family was introduced; existing actions keep their current authorization and confirmation behavior - no new frontend asset strategy was introduced; existing deploy flow with filament:assets remains unchanged Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #186
33 lines
1.8 KiB
PHP
33 lines
1.8 KiB
PHP
<?php
|
|
|
|
declare(strict_types=1);
|
|
|
|
use App\Support\Badges\BadgeCatalog;
|
|
use App\Support\Badges\BadgeDomain;
|
|
|
|
it('maps all evidence snapshot statuses and completeness states to known badge specs', function (BadgeDomain $domain, string $value): void {
|
|
$spec = BadgeCatalog::spec($domain, $value);
|
|
|
|
expect($spec->label)->not->toBe('Unknown')
|
|
->and($spec->icon)->not->toBeNull();
|
|
})->with([
|
|
'queued status' => [BadgeDomain::EvidenceSnapshotStatus, 'queued'],
|
|
'generating status' => [BadgeDomain::EvidenceSnapshotStatus, 'generating'],
|
|
'active status' => [BadgeDomain::EvidenceSnapshotStatus, 'active'],
|
|
'superseded status' => [BadgeDomain::EvidenceSnapshotStatus, 'superseded'],
|
|
'expired status' => [BadgeDomain::EvidenceSnapshotStatus, 'expired'],
|
|
'failed status' => [BadgeDomain::EvidenceSnapshotStatus, 'failed'],
|
|
'complete completeness' => [BadgeDomain::EvidenceCompleteness, 'complete'],
|
|
'partial completeness' => [BadgeDomain::EvidenceCompleteness, 'partial'],
|
|
'missing completeness' => [BadgeDomain::EvidenceCompleteness, 'missing'],
|
|
'stale completeness' => [BadgeDomain::EvidenceCompleteness, 'stale'],
|
|
]);
|
|
|
|
it('reclassifies valid-empty and freshness evidence states with explicit labels', function (): void {
|
|
expect(BadgeCatalog::spec(BadgeDomain::EvidenceCompleteness, 'complete')->label)->toBe('Coverage ready')
|
|
->and(BadgeCatalog::spec(BadgeDomain::EvidenceCompleteness, 'missing')->label)->toBe('Not collected yet')
|
|
->and(BadgeCatalog::spec(BadgeDomain::EvidenceCompleteness, 'missing')->color)->toBe('info')
|
|
->and(BadgeCatalog::spec(BadgeDomain::EvidenceCompleteness, 'stale')->label)->toBe('Refresh recommended')
|
|
->and(BadgeCatalog::spec(BadgeDomain::EvidenceCompleteness, 'stale')->color)->toBe('warning');
|
|
});
|