Add a mocked test suite covering every resource, and turn CI tests back on

[Cannonb4ll]

Why

The test suite was not running in CI. The step in .github/workflows/php_test.yml had been commented out, because the tests hit the live API: fork PRs have no token, and testServerRestart() restarts a real server. In practice only PHPStan was guarding the SDK.

There was also no way to intercept HTTP. Ploi::setApiToken() builds the Guzzle client internally and $guzzle is private, so no resource could be tested without a network call.

The seam

Ploi::setHandler(?callable $handler) accepts a Guzzle handler. Useful on its own for retry or logging middleware, and it is what lets the tests plug in a MockHandler.

The client is still assembled by setApiToken(), so the base URI, headers and http_errors setting under test are the ones users actually get — the tests are not asserting against a hand-rolled client. Production behaviour is unchanged when no handler is set.

Two suites

	runs	needs
tests/Unit	composer test, and CI	nothing
tests/Integration	composer test:integration	tests/.env with a real token

phpunit.xml sets defaultTestSuite="unit", so a bare phpunit no longer reaches for the network. The four existing live tests moved to tests/Integration unchanged apart from their namespace — they still have value as a check that the real API matches. HistoryTest never needed the network and moved to the unit suite.

Coverage

All 36 resource classes have a unit test. Per method it asserts the full URL, the HTTP verb and the decoded JSON body, plus the RequiresId paths:

public function testRunsAOneOffScriptAsAUser(): void
{
    $this->queue();

    $this->ploi->servers(1)->runOneOffScript('whoami', 'deployer');

    $this->assertRequest('post', 'servers/1/scripts/run', [
        'content' => 'whoami',
        'user'    => 'deployer',
    ]);
}

Tests\Unit\TestCase provides queue(), queueRaw(), queueMany(), request(), assertRequest(), assertRequestCount() and assertNoBody(). PloiTest covers the client itself: auth headers, base URI resolution, the supported verbs and every status-code-to-exception mapping. ResponseTest covers getJson() / getData() / toArray().

288 tests, 782 assertions, zero network calls, ~25ms.

PHPStan now covers the tests too

phpstan.neon picks up tests/ alongside src/, at the same level 5. Fixing what that surfaced turned up two real bugs in the live tests:

• SiteTest::testCreateExampleDotCom() discarded the result of its own recursive call and then fell off the end of a method declared : stdClass, so the @depends chain received null whenever it had to clean up a leftover site first. Its $foundSite flag was dead code — never set to true, so the break was unreachable.
• SshKeyTest::testDeleteSshKey() wrapped its only assertion in if (!empty($sshKey)) on a parameter typed stdClass, which can never be empty.

Resource::setId() and setIdOrFail() were declared : self, which resolves to Resource rather than the called class, so chaining off them lost the concrete type. They now carry @return static, which also helps anyone running static analysis against the SDK.

The remaining findings were assertions that could not fail — assertIsArray() on Response::toArray() and on getHistory(), both declared to return arrays — replaced with assertions that check something.

Verification

• composer test → OK (288 tests, 782 assertions)
• vendor/bin/phpstan analyse -c phpstan.neon (now src + tests) → [OK] No errors
• vendor/bin/phpcs --standard=PSR12 src → 130 errors, byte-identical to the master baseline; none added
• composer validate --strict → valid
• Checked for PHP 8-only syntax so the 7.4 leg of the matrix stays green