Adds browser fixture coverage for evidence system surfaces as described in Spec 376. Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #447
34 lines
1.9 KiB
Markdown
34 lines
1.9 KiB
Markdown
# Browser Verification Report
|
|
|
|
Status: PASS.
|
|
|
|
## Browser Harness
|
|
|
|
- Command: `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Browser/Spec376BrowserAuditFixtureCoverageSmokeTest.php`
|
|
- Result: pass, 2 tests, 21 assertions.
|
|
- Fixture family: `apps/platform/tests/Browser/Spec376BrowserAuditFixtureCoverageSmokeTest.php`
|
|
- Assertions: target text visible, no JavaScript errors, no console logs, screenshots captured.
|
|
|
|
## URLs Tested
|
|
|
|
| Page | URL pattern | Result |
|
|
|---|---|---|
|
|
| Evidence Snapshot View | `/admin/workspaces/{workspace}/environments/{environment}/evidence/{record}` | pass |
|
|
| Required Permissions | `/admin/workspaces/{workspace}/environments/{environment}/required-permissions` | pass |
|
|
| System Dashboard | `/system` | pass |
|
|
| System Operations | `/system/ops/runs` | pass |
|
|
| Provider Connection Detail | `/admin/provider-connections/{record}?environment_id={environment}` | pass |
|
|
|
|
## Screenshot Outputs
|
|
|
|
- `artifacts/screenshots/001-evidence-snapshot-view.png`
|
|
- `artifacts/screenshots/002-required-permissions.png`
|
|
- `artifacts/screenshots/003-system-dashboard.png`
|
|
- `artifacts/screenshots/004-system-operations.png`
|
|
- `artifacts/screenshots/005-provider-connection-detail.png`
|
|
|
|
## Notes
|
|
|
|
- First browser run failed because the Provider Connection detail assertion expected the more specific Required Permissions title. Repo truth from existing Spec 353 feature coverage shows the detail page uses the broader provider-readiness blocked heading. The assertion was corrected; product code was not changed.
|
|
- Sail saved screenshots under `apps/platform/tests/Browser/Screenshots/`. Because the Sail container is rooted at `apps/platform`, the spec-copy helper could not resolve host-level `specs/` without an explicit repo-root environment variable. The generated screenshots were copied into this spec artifact directory from the host workspace after the passing run.
|