15: End-to-end suite

[nikolaystrikhar]

What: 16 scenarios driving the library through the bootstrap a host runs — Config::set_hook_prefix(), Config::set_container(), Loader::register(), Loader::boot() — and then through the hooks boot() wired, dispatching plugins_loaded for the conflict step at priority 1 and the load pass at 2, all_admin_notices for the queue and wp_admin_notice_markup for the re-activation rewrite, against real active_plugins, core's own deactivate_plugins() and real site options; no source files, all tests.

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

$constant = $this->register( [ 'standalone_plugin_basename' => self::STANDALONE ] );

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

$this->assertNotContains( self::STANDALONE, $this->active_plugins() );
$this->assertSame( admin_url( 'plugins.php' ), $location );

$rendered = $this->render_admin_notices();  // do_action( 'all_admin_notices' )

$this->assertStringContainsString( 'has been deactivated', $rendered );
$this->assertSame( [], $this->notice_queue(), 'Rendering consumes the queue.' );

Why this way:

The hooks are dispatched, not the steps called. The earlier draft ran a request as Loader::run_conflict_resolution() followed by Loader::load_all(); a request is now do_action( 'plugins_loaded' ) and an admin page load do_action( 'all_admin_notices' ), 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, a resolution ordered behind the load pass — and calling the steps directly is exactly the arrangement that cannot see any of it. The container is handed over bare rather than pre-registered through WithContainer, for the same reason: boot() running the provider over it is one of the steps under test.

Each load-path test writes its own fixture file 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 fixture shared between two tests lets the second pass without loading anything — including if the load logic were deleted outright — and a reused constant makes a later sub-plugin read as already loaded. 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.

The host-binding tests assert the defaults did not run. Across the two of them a host binds seven of the library's registrations — registrar, plugin checker, deactivator, notice queue, activator, gatekeeper and resolver — and each is asserted to be the object the request reached. On their own those positive assertions would hold just as well if the library had also resolved a second, default copy behind the host's back, so the standalone is left really active, and the test asserts active_plugins still contains it, the default queue is empty and the activation record is empty.

exit is never mocked, even end to end. wp_safe_redirect throws instead, which stops the request where production stops it: run_halted_request() returns where the user was sent and asserts the destination, while run_request() installs the same throwing stub for every request that must not redirect and fails the test if one does. preventExit() would let a request carry on past the line production never returns from, which turns a failure into a pass.

Four preconditions decide whether any of this means anything, so setUp establishes all four. An interactive admin GET and a user who can activate_plugins, or Conflict\Gatekeeper turns every policy scenario away and they pass while resolving nothing; the hook prefix, which both plugins_loaded steps and both option names derive from; and a rewound plugins_loaded counter, because the harness dispatched that hook before any test ran and boot() would rightly report it is too late to wire. All four are process-global, and all four are restored in tearDown rather than at the end of a test body.

[nikolaystrikhar]

Superseded by #28, #29 and #30, which split this into three reviewable branches on top of the restacked 14.