Symfony bundle to isolate doctrine database tests and improve test performance

Installs: 21 472 093

Dependents: 114

Suggesters: 3

Security: 0

Stars: 1 065

Watchers: 8

Forks: 60

Open Issues: 6


v8.2.0 2024-05-28 15:41 UTC


PHP Version Stable release

What does it do? 😊

This bundle provides features that help you run your Symfony-framework-based App's testsuite more efficiently with isolated tests.

It provides a StaticDriver that will wrap your originally configured Driver class (like DBAL\Driver\PDOMysql\Driver) and keeps a database connection statically in the current php process.

With the help of a PHPUnit extension class it will begin a transaction before every testcase and roll it back again after the test finished for all configured DBAL connections. This results in a performance boost as there is no need to rebuild the schema, import a backup SQL dump or re-insert fixtures before every testcase. As long as you avoid issuing DDL queries that might result in implicit transaction commits (Like ALTER TABLE, DROP TABLE etc; see https://wiki.postgresql.org/wiki/Transactional_DDL_in_PostgreSQL:_A_Competitive_Analysis) your tests will be isolated and all see the same database state.

It also includes a Psr6StaticArrayCache that will be automatically configured as meta data & query cache for all EntityManagers. This improved the speed and memory usage for my testsuites dramatically! This is especially beneficial if you have a lot of tests that boot kernels (like Controller tests or ContainerAware tests) and use Doctrine entities.

How to install and use this Bundle?

  1. install via composer
composer require --dev dama/doctrine-test-bundle
  1. If you're not using Flex, enable the bundle by adding the class to bundles.php
// config/bundles.php

return [
    DAMA\DoctrineTestBundle\DAMADoctrineTestBundle::class => ['test' => true],
  1. Starting from version 8 and only when using DBAL < 4 you need to make sure you have use_savepoints enabled on your doctrine DBAL configuration for all relevant connections:
               use_savepoints: true

Using the Bundle with PHPUnit

  1. Add the Extension to your PHPUnit XML config

    • PHPUnit 8 or 9:

              <extension class="DAMA\DoctrineTestBundle\PHPUnit\PHPUnitExtension" />
    • PHPUnit 10+:

              <bootstrap class="DAMA\DoctrineTestBundle\PHPUnit\PHPUnitExtension" />
  2. Make sure you also have phpunit/phpunit available as a dev dependency (versions 8, 9 and 10 are supported with the built-in extension) to run your tests. Alternatively this bundle is also compatible with symfony/phpunit-bridge and its simple-phpunit script. (Note: you may need to make sure the phpunit-bridge requires the correct PHPUnit 8+ Version using the environment variable SYMFONY_PHPUNIT_VERSION).

  3. That's it! From now on whatever changes you do to the database within each single testcase (be it a WebTestCase or a KernelTestCase or any custom test) are automatically rolled back for you 😊

Using the Bundle with Behat

Enable the extension in your Behat config (e.g. behat.yml)

   # ...
       DAMA\DoctrineTestBundle\Behat\ServiceContainer\DoctrineExtension: ~

That's it! From now on whatever changes you do to the database within each scenario are automatically rolled back for you.

Please note that this is only works if the tests are executed in the same process as Behat. This means it cannot work when using e.g. Selenium to call your application.


The bundle exposes a configuration that looks like this by default:

    enable_static_connection: true
    enable_static_meta_data_cache: true
    enable_static_query_cache: true

Setting enable_static_connection: true means it will enable it for all configured doctrine dbal connections.

You can selectively only enable it for some connections if required:

        connection_a: true

Controlling how connections are kept statically in the current php process

By default, every configured doctrine DBAL connection will have its own driver connection that is managed in the current php process. In case you need to customize this behavior you can choose different "connection keys" that are used to select driver connections.

Example for 2 connections that will re-use the same driver connection instance:

                url: '%database.url1%'

                url: '%database.url2%'

        # assigning the same key will result in the same internal driver connection being re-used for both DBAL connections
        default: custom_key
        foo: custom_key

Since v8.1.0: For connections with read/write replicas the bundle will use the same underlying driver connection by default for the primary and also for replicas. This addresses an issue where inconsistencies happened when reading/writing to different connections. This can also be customized as follows:

                url: '%database.url%'
                        url: '%database.url_replica%'

        # assigning different keys will result in separate internal driver connections being used for primary and replica
            primary: custom_key_primary
                replica_one: custom_key_replica


An example usage can be seen within the functional tests included in this bundle: https://github.com/dmaicher/doctrine-test-bundle/tree/master/tests

This bundle is also used on the official Symfony Demo testsuite: https://github.com/symfony/demo


Sometimes it can be useful to be able to debug the database contents when a test failed. As normally all changes are rolled back automatically you can do this manually:

public function testMyTestCaseThatINeedToDebug()
    // ... something thats changes the DB state
    // now the DB changes are actually persisted and you can debug them


In case you are running (maybe without knowing it) queries during your tests that are implicitly committing any open transaction (see https://dev.mysql.com/doc/refman/8.0/en/implicit-commit.html for example) you might see an error like this:

Doctrine\DBAL\Driver\PDOException: SQLSTATE[42000]: Syntax error or access violation: 1305 SAVEPOINT DOCTRINE2_SAVEPOINT_2 does not exist

Currently there is no way for this bundle to work with those queries as they simply cannot be rolled back after the test case finished.

See also #58