ahmido
b182f55562
## Summary - add an in-place Required Permissions assist to the onboarding Verify Access step via a Filament slideover - route permission-related verification remediation links into the assist first and keep deep-dive links opening in a new tab - add view-model and link-behavior helpers plus focused feature, browser, RBAC, and unit coverage for the new assist ## Scope - onboarding wizard Verify Access UX - Required Permissions assist rendering and link behavior - Spec 139 artifacts, contracts, and checklist updates ## Notes - branch: `139-verify-access-permissions-assist` - commit: `b4193f1` - worktree was clean at PR creation time Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #168
51 lines
2.4 KiB
Markdown
51 lines
2.4 KiB
Markdown
# Quickstart — Spec 139 (Verify Access Required Permissions Assist)
|
|
|
|
## Local run (Sail)
|
|
|
|
- Start services: `vendor/bin/sail up -d`
|
|
- Open the app: `vendor/bin/sail open`
|
|
|
|
## Where to click
|
|
|
|
1. Sign in to the admin panel and select a workspace.
|
|
2. Open a managed tenant onboarding draft that is on the `Verify access` step.
|
|
3. Use a tenant/provider connection combination that produces permission-related blocked or needs-attention verification results.
|
|
4. In `Verify access`, confirm `View required permissions` appears near the verification result.
|
|
5. Open the assist and verify:
|
|
- summary metadata is visible,
|
|
- missing application and/or delegated permissions render when present,
|
|
- copy actions only appear when a payload exists,
|
|
- the full-page deep dive is visibly secondary.
|
|
6. Open the full-page deep dive and confirm it launches in a new tab while the onboarding tab remains usable.
|
|
7. Close the assist and rerun verification to confirm normal continuity.
|
|
8. Inspect permission-related Verify Access report next steps and confirm they open the in-place assist instead of navigating away.
|
|
9. Inside the assist, confirm deep-dive actions clearly communicate their new-tab behavior before activation.
|
|
|
|
## Expected behavior
|
|
|
|
- Fully ready verification with no permission guidance: no assist is shown.
|
|
- Permission-blocked or permission-relevant needs-attention verification: assist is shown.
|
|
- Permission-related remediation controls from Verify Access open the assist in place.
|
|
- Internal and external deep-dive links exposed from the assist continue opening in a new tab.
|
|
- Assist deep-dive links communicate their new-tab behavior clearly in the UI.
|
|
- Closing the assist preserves the current wizard step.
|
|
|
|
## Targeted tests
|
|
|
|
- Feature / Livewire:
|
|
- `vendor/bin/sail artisan test --compact tests/Feature/Onboarding/OnboardingVerificationTest.php`
|
|
- `vendor/bin/sail artisan test --compact tests/Feature/Onboarding/OnboardingVerificationClustersTest.php`
|
|
- `vendor/bin/sail artisan test --compact tests/Feature/Onboarding/OnboardingVerificationV1_5UxTest.php`
|
|
- Browser:
|
|
- `vendor/bin/sail artisan test --compact tests/Browser/OnboardingDraftVerificationResumeTest.php`
|
|
|
|
## Formatting
|
|
|
|
- `vendor/bin/sail bin pint --dirty --format agent`
|
|
|
|
## Deploy notes
|
|
|
|
- No new route registration.
|
|
- No new Filament asset registration expected.
|
|
- If implementation later adds registered assets for the assist, deployment must include `php artisan filament:assets`.
|