15A: Scenario suite — the load path, end to end

[nikolaystrikhar]

What: a tests/unit/Scenario/ suite that bootstraps the library the way a host does — Config::set_hook_prefix(), Config::set_container(), Absorber::register(), Absorber::boot() — and then reaches it only through the hooks boot() wired, dispatching plugins_loaded for the load pass and all_admin_notices for the notices, against a real active_plugins, real site options and real files on disk; six load-path scenarios, the shared Bootstrap_Test_Case, an @after fixture cleanup, and the tests/README section every case is written up in.

Usage: the shape of a scenario — a bootstrap, a request, and assertions against what WordPress actually holds afterwards.

$constant = $this->register( [ 'activation_callback' => $record ] );

$this->boot();          // set_container() with a bare container, then boot()
$this->run_request();   // do_action( 'plugins_loaded' )

$this->assertSame( 1, $this->bundled_plugin_loads() );
$this->assertTrue( defined( $constant ) );
$this->assertSame( [ self::SLUG => true ], $this->activation_record() );

Why this way:

The hooks are dispatched, not the steps called. A request is do_action( 'plugins_loaded' ), so what runs is whatever boot() wired, in the order and at the priorities it wired it. That is the half where the bugs are — an admin-only add_action() that never ran, a step wired into a dispatch window that had already closed — and calling Loader::load_all() directly is exactly the arrangement that cannot see any of it. The container is handed over bare rather than pre-registered, for the same reason: boot() running the provider over it is one of the steps under test.

Neither request helper catches the redirect, because it cannot. Every plugins_loaded step wraps itself in catch ( Throwable ) so a hook this library owns can never white-screen a site — which means a stubbed redirect is swallowed and reported before it could leave the step, and a catch around the dispatch would pass whether or not the request redirected. Both helpers watch for the halt where the library announces it and assert both halves: that something reported, and that what it reported was this halt rather than some other failure inside the step.

The halted helper empties plugins_loaded before it throws. exit means the load pass one priority behind does not run either, so a scenario asserting nothing loaded after a redirect would otherwise be asserting it about a request production never serves. The hook is put back afterwards, since emptying it is a statement about that request and not about the process.

Each scenario writes its own fixture and its own guard constant. require_once dedupes by resolved path for the lifetime of the process and define() lasts just as long, so a shared fixture lets a later scenario pass without loading anything — including if the load logic were deleted outright. WithBundledPlugins now cleans up on its own @after hook rather than trusting a caller's tearDown: a failed assertion aborts the test where it stands, so a cleanup line at the end of a body is the one that does not run on the day it matters.