Files
git.stella-ops.org/docs/features/checked/web/configuration-pane.md
2026-02-12 10:27:23 +02:00

70 lines
3.4 KiB
Markdown

# Configuration Pane (Integration Status Dashboard)
## Module
Web
## Status
VERIFIED
## Description
Console-level configuration pane showing integration status grouped by sections with connection health, detail views per integration, and a state management service for tracking configuration changes.
## Implementation Details
- **Feature directory**: `src/Web/StellaOps.Web/src/app/features/configuration-pane/`
- **Routes**: `configuration-pane.routes.ts`
- **Components**:
- `configuration-pane` (`src/Web/StellaOps.Web/src/app/features/configuration-pane/components/configuration-pane.component.ts`)
- `integration-detail` (`src/Web/StellaOps.Web/src/app/features/configuration-pane/components/integration-detail.component.ts`)
- `integration-section` (`src/Web/StellaOps.Web/src/app/features/configuration-pane/components/integration-section.component.ts`)
- **Services**:
- `configuration-pane-api` (`src/Web/StellaOps.Web/src/app/features/configuration-pane/services/configuration-pane-api.service.ts`)
- `configuration-pane-state` (`src/Web/StellaOps.Web/src/app/features/configuration-pane/services/configuration-pane-state.service.ts`)
- **Models**:
- `src/Web/StellaOps.Web/src/app/features/configuration-pane/models/configuration-pane.models.ts`
- **Source**: Feature matrix scan
## E2E Test Plan
- **Setup**:
- [ ] Log in with a user that has appropriate permissions
- [ ] Navigate to `/console/configuration`
- [ ] Ensure test data exists (scanned artifacts, SBOM data, or seed data as needed)
- **Core verification**:
- [ ] Verify settings form loads with current values pre-populated
- [ ] Verify changes can be saved and persist across page reloads
- [ ] Verify validation prevents saving invalid configurations
- **Edge cases**:
- [ ] Verify graceful handling when backend API is unavailable (error state)
- [ ] Verify responsive layout at different viewport sizes
- [ ] Verify accessibility (keyboard navigation, screen reader labels, ARIA attributes)
## Verification
- Date: 2026-02-10
- Run artifacts: docs/qa/feature-checks/runs/web/configuration-pane/run-001/
- Tier results:
- tier0-source-check.json: pass
- tier1-build-check.json: pass
- tier2-e2e-check.json: pass
## Recheck (run-003)
- Date (UTC): 2026-02-11T06:37:41Z
- Status: FAILED (strict Tier 2 UI replay)
- Tier 2 evidence: `docs/qa/feature-checks/runs/web/configuration-pane/run-003/tier2-ui-check.json`
- Notes: `/console/configuration` failed strict end-user assertion because the `Configuration` heading never rendered during the Playwright transaction.
## Recheck (run-004)
- Date (UTC): 2026-02-11
- Status: VERIFIED (strict Tier 2 UI replay)
- Tier 1 evidence: Focused configuration-pane suite passed 3/3 across 1 file.
- Tier 2 evidence: `docs/qa/feature-checks/runs/web/configuration-pane/run-004/tier2-ui-check.json`
- Replay scope:
- Navigate to `/settings/configuration-pane` and verify heading, summary metrics, and integration list render.
- Verify `Primary Database` row using scoped `.integration-name` selector.
- Open integration detail panel and verify `Edit Configuration` action is visible.
## Recheck (run-007)
- Date (UTC): 2026-02-11T10:08:09Z
- Status: PASSED (strict Tier 2 UI replay)
- Tier 2 evidence: docs/qa/feature-checks/runs/web/configuration-pane/run-007/tier2-ui-check.json
- Notes: Verified on /settings/configuration-pane with configuration summary and detail-panel interaction assertions.