[BUG] Unit tests not working when using :memory: driver sqlite database.

[bigperson]

Package version, Laravel version

Laravel 5.5
Laravel doctrine 1.4
PHPUnit 6.0

Expected behaviour

Tests must pass success.

Actual behaviour

Entity manager can not access the tables in databases
Errors:

 Doctrine\DBAL\Driver\PDOException: SQLSTATE[HY000]: General error: 1 no such table: cities

Steps to reproduce the behaviour

/config/database.php

...
'connections' => [
...
        'tests' => [
            'driver' => 'sqlite',
            'database' => ':memory:',
            'prefix' => '',
        ],
...

/config/doctrine.php

...
'connection'    => env('DB_CONNECTION', 'mysql'),
...

phpunit.xml

<env name="DB_CONNECTION" value="tests"/>

ExampleTest.php

/** @var \Doctrine\ORM\EntityManagerInterface */
    protected $em;

    /**
     * @return void
     */
    public function setUp()
    {
        parent::setUp();
        $this->em = $this->app->make(EntityManagerInterface::class);
    }

    /**
     * {@inheritDoc}
     */
    protected function tearDown()
    {
        parent::tearDown();

        $this->em->close();
        $this->em = null;
    }

    /**
     * A basic test example.
     *
     * @return void
     */
    public function testBasicTest()
    {
        \DB::table('cities')->insert(['name'=>'test']); //Working
        entity(City::class)->create(); //crashed
        $city = (new City())->setName('test');
        $this->em->persist($city);
        $this->em->flush(); //crashed
        $cities = $this->em->getRepository(City::class)->findAll(); //crashed

        $this->assertCount(3, $cities);
    }

[elambro]

Do you have a 'create_cities_table' migration?

[bicatu]

I have similar issue (not same table of course), but I do have the VersionXXX files that when I run from the console create the tables I am looking for. (when I call the same methods myself not from phpunit they work)

[garret-gunter]

I don't see where you are running the migrations. We use in memory sqlite for our tests. We haven't had this issue. Have you tried adding the helper trait for refreshing the database during tests? It should be in the laravel doctrine migrations package.

[patrickbrouwers]

Cannot reproduce

[dallincoons]

I have the same issue, I had to use a sqlite file instead of the in-memory version. I'm using Orchestra Testbench.

[nospoon]

I think this might be related to running the tests inside vm.

[R3VoLuT1OneR]

I have same problem.
Doctrine connection and Laravel DatabaseManager connections have different PDOConnection.
So Illuminate\Foundation\Testing\RefreshDatabase trait not working.
So tests not working with default Laravel migrations.

[patrickbrouwers]

You cannot use that trait as indeed we don't share the PDOConnection

[xxRockOnxx]

Any workaround available yet? I'm having this problem also. Can confirm this is a bug.

More info:

setUp()
{
    parent::setUp();
    Artisan::call('migrate'); // Works properly
    \DB::statement('SELECT * FROM tablename'); // works fine

     // Scenario 2
     parent::setUp();
     \DB::statement('SELECT * FROM tablename'); // Exception
}

This just confirms it again. Not sure whether it is laravel-doctrine's problem or doctrine itself.

[Stolz]

This is my workaround so far. Provided you set up phpunit.xml and config/database.php as @bigperson mentioned, in order to have the RefreshDatabase behavior working with Docrine make your tests to use this trait instead of Illuminate\Foundation\Testing\RefreshDatabase

<?php

namespace Tests\Traits;

use Illuminate\Contracts\Console\Kernel;

trait RefreshDatabase
{
    use \Illuminate\Foundation\Testing\RefreshDatabase;

    /**
     * Begin a database transaction on the testing database.
     *
     * @return void
     */
    public function beginDatabaseTransaction()
    {
        $connection = $this->app->make('em')->getConnection();
        $connection->beginTransaction();
        
        $this->beforeApplicationDestroyed(function () use ($connection) {
            $connection->rollBack();
        });
    }

    /**
     * Refresh the in-memory database.
     *
     * @return void
     */
    protected function refreshInMemoryDatabase()
    {
        $this->artisan('doctrine:schema:create');

        $this->app[Kernel::class]->setArtisan(null);
    }
}

It works without problems is several of my projects although for others I get Operation 'Doctrine\DBAL\Platforms\AbstractPlatform::getCreateSequenceSQL' is not supported by platform error but at least DB schema seems to be successfully created in memory and my tests run faster now.

If anyone has a better approach please let me know.

[bicatu]

Hi, any updates on this one?