ahmido
1debe40ced
## Summary - implement the provider capability registry and derived capability evaluation flow - update provider connections, onboarding, required-permissions diagnostics, and provider blocker translation to use capability-first summaries - add bounded unit, feature, and browser test coverage plus the prepared Spec 283 artifacts ## Notes - branch: `283-provider-capability-registry` - commit: `74e75c3e` - no additional validation commands were run in this git/PR flow step Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #342
21 lines
718 B
PHP
21 lines
718 B
PHP
<?php
|
|
|
|
declare(strict_types=1);
|
|
|
|
use App\Support\Links\RequiredPermissionsLinks;
|
|
use Illuminate\Foundation\Testing\RefreshDatabase;
|
|
|
|
uses(RefreshDatabase::class);
|
|
|
|
it('renders required permissions with provider capability grouping before raw permission detail', function (): void {
|
|
[$user, $tenant] = createUserWithTenant(role: 'readonly');
|
|
|
|
$this->actingAs($user)
|
|
->get(RequiredPermissionsLinks::requiredPermissions($tenant, ['status' => 'all']))
|
|
->assertSuccessful()
|
|
->assertSee('Provider capabilities')
|
|
->assertSee('Inventory read')
|
|
->assertSee('Directory role definitions read')
|
|
->assertSeeInOrder(['Provider capabilities', 'Technical details'], false);
|
|
});
|