feat(bridge): add Mockery bridge (testo/bridge-mockery)

[rossaddison]

Closes #41

What this adds

A new bridge/mockery/ package (testo/bridge-mockery) that integrates Mockery into Testo.

How it works

MockeryPlugin registers MockeryInterceptor as a TestRunInterceptor. The interceptor wraps every test in a try/finally and calls Mockery::close() after each one — whether it passed or failed. This ensures:

• Unfulfilled mock expectations are reported as test failures.
• The Mockery container is cleared between tests, preventing state leaking from one test into the next.

Usage

// testo.php
return new ApplicationConfig(
    plugins: [new \Testo\Bridge\Mockery\MockeryPlugin()],
    suites:  [new SuiteConfig(name: 'Unit', location: ['tests/Unit'])],
);

#[Test]
final class MyServiceTest
{
    public function callsRepository(): void
    {
        $repo = \Mockery::mock(UserRepository::class);
        $repo->expects('find')->with(1)->andReturn(new User(1));

        $service = new UserService($repo);
        $service->getUser(1);
        // Mockery::close() is called automatically — expectation is verified here
    }
}

Files

File	Purpose
bridge/mockery/composer.json	Package definition (testo/bridge-mockery)
bridge/mockery/src/MockeryPlugin.php	PluginConfigurator — entry point users register
bridge/mockery/src/Internal/MockeryInterceptor.php	TestRunInterceptor — calls Mockery::close() in finally
bridge/mockery/tests/Acceptance/MockeryBridgeTest.php	Acceptance tests: mock, spy, container isolation

The bridge follows the same structure and conventions as the existing bridge/symfony-console and plugin/lifecycle packages.

[Copilot]

Pull request overview

Adds a new testo/bridge-mockery package that integrates Mockery into Testo by registering a TestRunInterceptor intended to call Mockery::close() after each test, plus initial acceptance tests and root composer wiring.

Changes:

• Add testo/bridge-mockery to the monorepo (package composer.json, plugin, interceptor, changelog).
• Wire the new bridge into the root repo dev dependencies / suggestions and test autoloading.
• Add initial acceptance tests and a dedicated suites definition for the bridge.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
composer.json	Adds the bridge as a dev dependency + suggestion, and adds test autoload mapping.
bridge/mockery/composer.json	Defines the new testo/bridge-mockery package and its dependencies.
bridge/mockery/src/MockeryPlugin.php	Plugin entry point registering the interceptor into the pipeline.
bridge/mockery/src/Internal/MockeryInterceptor.php	Interceptor intended to ensure Mockery::close() runs after each test.
bridge/mockery/tests/suites.php	Declares the acceptance test suite for the bridge package.
bridge/mockery/tests/Acceptance/MockeryBridgeTest.php	Acceptance tests demonstrating mock/spy usage and intended teardown behavior.
bridge/mockery/CHANGELOG.md	Adds initial changelog for version 0.1.0.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
bridge/mockery/src/MockeryPlugin.php	0.00%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[roxblnfk]

The docs is there https://php-testo.github.io/docs/bridge/mockery
Thanks

[rossaddison]

Installed and wired up in a production Yii3 invoice application today. Setup was exactly as documented — one plugin registration in testo.php and no per-test teardown in any test class.

First real-world test suite — three scenarios for As4RetryEngine::detectMissingReceipts(), all running against interface mocks with no database:

#[Test]
final class As4RetryEngineTest
{
    public function detectMissingReceiptsReturnsZeroForEmptyQueue(): void
    {
        $repo = m::mock(As4MessageRepositoryInterface::class);
        /** @var \Mockery\Expectation $e */
        $e = $repo->shouldReceive('findAwaitingReceipts');
        $e->once()->andReturn([]);

        $engine = new As4RetryEngine($repo, m::spy(As4SenderInterface::class), ...);
        Assert::same(0, $engine->detectMissingReceipts());
    }
    // ...
}

One Psalm note worth documenting: shouldReceive() is typed as returning Expectation|ExpectationInterface|HigherOrderMessage. At Psalm errorLevel 1, calling ->once() or ->andReturn() on that union fails because not every member of the union declares those methods. The workaround is a @var \Mockery\Expectation annotation on the intermediate variable before chaining. Not a blocker, but a note for anyone running strict Psalm in their test suite.

The spy pattern for don't-care dependencies (m::spy(LoggerInterface::class)) was particularly clean — no stub boilerplate for collaborators that aren't under test.