ahmido
29ad8852ca
## Summary - integrate the current `platform-dev` branch into `dev` - bring the latest platform work from the integration branch into the main development branch - include the recent findings lifecycle backfill removal slice together with the already accumulated `platform-dev` changes ## Scope - source branch: `platform-dev` - target branch: `dev` - branch role: integration PR, not a single-feature PR ## Validation - branch state reviewed before PR creation - `platform-dev` is ahead of `dev` with the expected integration history - this PR intentionally carries the accumulated `platform-dev` commits into `dev` ## Notes - this is the correct merge direction for the current workflow, where feature branches land in `platform-dev` first and `platform-dev` is then merged into `dev` - after merging, `platform-dev` can be recreated fresh from `dev` as usual Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #295
15 lines
629 B
PHP
15 lines
629 B
PHP
<?php
|
|
|
|
declare(strict_types=1);
|
|
|
|
use App\Support\Auth\PlatformCapabilities;
|
|
|
|
it('removes the platform capability and seeder grant for findings lifecycle backfill', function (): void {
|
|
expect(defined(PlatformCapabilities::class.'::RUNBOOKS_FINDINGS_LIFECYCLE_BACKFILL'))->toBeFalse()
|
|
->and(PlatformCapabilities::all())->not->toContain('platform.runbooks.findings.lifecycle_backfill');
|
|
|
|
expect((string) file_get_contents(database_path('seeders/PlatformUserSeeder.php')))
|
|
->not->toContain('RUNBOOKS_FINDINGS_LIFECYCLE_BACKFILL')
|
|
->not->toContain('platform.runbooks.findings.lifecycle_backfill');
|
|
});
|