Wojciech Sznapka Blog – PHP / Symfony 2 / Open Source

Please email if you reply AND install the subscribe to comments plugin of you wp blog. Thanks.

right I fully agree! Thanks! oh by the way I was thinking on the improvement of these classes but don’t know if it is possible
check the note on my blog post http://www.craftitonline.com about improving the classes.

wow nice way of initializing the entity manager, I could have not come up with that that easy, i will keep it in mind when doing integration tests. I would though try first the app booting approach since it makes it simpler but slower.

In addition to the methods already mentioned, you can also use a WebTestCase (which, by default, uses all the configuration for your test environment) and setup up the database in the following way:
$client = static::createClient();
$container = $client->getContainer();
$doctrine = $container->get(‘doctrine’);
$em = $doctrine->getEntityManager();

$schemaTool = new SchemaTool($em);

$mdf = $em->getMetadataFactory();
$classes = $mdf->getAllMetadata();

$schemaTool->dropDatabase();
$schemaTool->createSchema($classes);

You probably want to put this stuff in a custom setUp() method in an abstract class that inherits from WebTestCase.

Yes, that’s functional tests. But they are also needed, after all unit tests have been written – to test configuration, valid integration etc.

Hi Josef,

have you got your fixtures dir in same dir as BaseTestCase?

Try to echo result of the $this->runConsole(„doctrine:fixtures:load”, array(„–fixtures” => __DIR__ . „/../DataFixtures”)); so we will know what is happening :-)

Lucas, not yet, but I’ll check it. It looks promising

I came up with this after reading the article and the comments. I’m still not sure where to put the class (I currently have it in one of the bundle’s Test dir but I think it should go somewere under app/)

require_once(__DIR__ . „/../../../../app/AppKernel.php”);

use DoctrineORMToolsSchemaTool;

use SymfonyBundleFrameworkBundleTestWebTestCase;

abstract class BaseServiceTest extends WebTestCase {

protected $_container;

public function setUp()
{
$client = static::createClient();
$this->_container = $client->getContainer();
$doctrine = $this->_container->get(‘doctrine’);
$em = $doctrine->getEntityManager();
$schemaTool = new SchemaTool($em);

$mdf = $em->getMetadataFactory();
$classes = $mdf->getAllMetadata();

$schemaTool->dropDatabase();
$schemaTool->createSchema($classes);

//Load all fixtures
$kernel = $client->getKernel();
$application = new SymfonyBundleFrameworkBundleConsoleApplication($kernel);
$application->setAutoExit(false);
$options = array(‘command’ => ‘doctrine:fixtures:load’);
$application->run(new SymfonyComponentConsoleInputArrayInput($options));

}

protected function get($service)
{
return $this->_container->get($service);
}
}

In this case, I’m mixing both solutions, to create a test class with access to the container via the get method and with a clean DB created and all fixtures loaded.

It’s still missing if you want to load specific fixtures for testing, but I’ll start like this and see. BTW, first time writing test in Symfony 2, and still learning the framework.

I have written a Fixture autoloading TestCase class, which is specifically using MongoDB in my case, but might easily be changed to use anything.

https://gist.github.com/3305223