Tests with the Container

Yo Vlad!

Hmm, I don't think this is possible - without basically sub-classing the ORMPurger and overriding the purge() method. But I get your use-case - it's really common for "look-up" tables - things that are effectively static, that you don't want to "clean out" every single time. Let me throw out a few options:

1) There must be *some* way that you originally pre-populated these tables - and a new developer would need these (e.g. SQL files) to populate *their* database. You could drop *all* the data, but then execute these SQL files automatically right after the purge

2) Override ORMPurger and avoid dropping the data in those tables. It's possible you'll run into constraint problems, but probably not (I'm guessing your configuration tables don't have foreign key columns to *other* tables that are being cleared).

Hopefully one of these looks appetizing for you - there's unfortunately no little config option for this :)

Cheers!

Hi Ryan,

This can also be accomplished with two entity managers and having the corresponding entities in different subdirectories.

This post talks about it: http://stackoverflow.com/questions/12220198/using-doctrine-2-entity-with-different-databases with two databases, but the same thing can be set up with a single database and two entity managers.

Then in the <strong>purgeDatabase()</strong> method we'd have to purge using one entity manager and skip purging with the other.

Regarding your #1 point, I also have methods that restore the original tables from backup tables using "<strong>INSERT SELECT</strong>" SQL queries:

/** @var Connection $connection */
$connection = $this->getEntityManager()->getConnection();

/** @var Statement $statement */
$statement = $connection->prepare($query);
$statement->execute();

Thank you!

Ha, very clever Vlad! That makes perfect sense - but I didn't think of it :). I'm not sure if you'll run into issues if you ever need to join across entities in the 2 different entity managers - but this may also not be something you need :).

Thanks for sharing this!

Hi Theirno!

Hmm! That error comes from inside the KernelTestCase class: https://github.com/symfony/....

Basically, it is looking for your phpunit.xml or phpunit.xml.dist file. What command are you using to execute phpunit? Do you have any non-traditional directory structure?

Cheers!

Hi,

The same issue

Cmd used : php bin/phpunit src/AppBundle/Tests/Controller/Api/ProgrammerControllerTest.php

HI Amine

I was able to make it work, with these steps:

1) Create a phpunit.xml with this content:

<?xml version="1.0" encoding="UTF-8"?>
<phpunit colors="true">
    <php>
        <server name="KERNEL_DIR" value="app" />
    </php>
</phpunit>

2) Run composer require indigophp/doctrine-annotation-autoload
3) Run composer dump-autoload

Hey Amine
Could you try running and see what happens

php vendor/bin/phpunit -c src/AppBundle/Tests/Controller/Api/ProgrammerControllerTest.php

Cheers!