Which service override pattern substitutes the database adapter in laminas integration tests without production credentials?

Answer

The pattern that substitutes the production database adapter without credentials is to replace the Zend\Db\Adapter\Adapter (or Laminas\Db\Adapter\Adapter in v3+) service in the ServiceManager with a factory that returns a PDO SQLite adapter pointing to an in‑memory database.

Steps to apply the override

1. Determine the exact service name for your Laminas version:
   • Laminas‑Db v2.x (or Zend Framework): service name Zend\Db\Adapter\Adapter
   • Laminas‑Db v3.x+: service name Laminas\Db\Adapter\Adapter
2. Create a test‑specific configuration file, e.g. config/autoload/module.test.db.php:

return [
    'service_manager' => [
        'factories' => [
            // Replace the adapter service with a SQLite in‑memory factory
            'Zend\Db\Adapter\Adapter' => function ($sm) {
                return new Laminas\Db\Adapter\Adapter([
                    'driver' => 'pdo_sqlite',
                    'database' => ':memory:',
                ]);
            },
            // If you are on v3+, also provide the Laminas‑namespaced alias
            'Laminas\Db\Adapter\Adapter' => function ($sm) {
                return $sm->get('Zend\Db\Adapter\Adapter');
            },
        ],
    ],
];

1. Ensure this file is loaded only in the test environment. In tests/TestBootstrap.php (or your PHPUnit bootstrap) add:

// After loading the application config, merge the test override
$config = array_merge_recursive(
    $appConfig,
    include 'config/autoload/module.test.db.php'
);

1. Run your integration tests; the ServiceManager will now return the SQLite adapter whenever $sm->get('Zend\Db\Adapter\Adapter') (or the Laminas alias) is requested.

What this pattern preserves

The override only changes the adapter factory; all other services that depend on the adapter (e.g., table gateways, repositories, controllers) receive the same injected instance, keeping the production ServiceManager composition intact.

Considerations

• SQLite’s dialect differs from MySQL/PostgreSQL (e.g., lack of full‑support for CTEs, different type casting). Tests that rely on vendor‑specific SQL will need to be reviewed or mocked.
• Version mismatches between laminas-db, laminas-mvc, and laminas-test can change the service name or factory signatures; verify the exact class names in your project.
• If the test bootstrap inadvertently loads a production local.php after the override, credentials could leak. Keep test configuration isolated.

Missing diagnostic detail

To confirm the correct service name to override, please specify the major version of laminas-db (or Zend Db) you are using.