ahmido
564da05096
This PR introduces the Operation Run Actionability System. Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #439
28 lines
1.1 KiB
Markdown
28 lines
1.1 KiB
Markdown
# Browser Smoke Notes
|
|
|
|
Date: 2026-06-08
|
|
Command:
|
|
|
|
```bash
|
|
cd apps/platform && ./vendor/bin/sail php vendor/bin/pest tests/Browser/Spec367OperationRunActionabilitySmokeTest.php
|
|
```
|
|
|
|
Result: 1 passed, 11 assertions.
|
|
|
|
## Path
|
|
|
|
- Authenticated as an operations-capable user.
|
|
- Visited the environment dashboard via `EnvironmentDashboard::getUrl(tenant: $tenant)`.
|
|
- Visited the Operations page through `OperationRunLinks::index(...)` with the current terminal follow-up tab selected.
|
|
|
|
## Assertions
|
|
|
|
- The dashboard loaded without JavaScript/runtime errors.
|
|
- Operations needing attention were visible when a current terminal problem existed.
|
|
- A superseded Provider Connection blocker did not keep generating a current CTA.
|
|
- The Operations current terminal follow-up tab showed the current policy failure.
|
|
- Resolved or superseded terminal history stayed out of the current follow-up list.
|
|
- Workspace/tenant context remained scoped through the tested links.
|
|
|
|
No screenshot artifact was retained because the bounded browser proof is assertion-based and no screenshot deliverable was required.
|