WARNING:
You are browsing the documentation for Symfony 3.1
which is not maintained anymore.
Consider upgrading your projects to Symfony 4.3.
How to Test Doctrine Repositories
How to Test Doctrine Repositories¶
Unit testing Doctrine repositories in a Symfony project is not recommended. When you're dealing with a repository, you're really dealing with something that's meant to be tested against a real database connection.
Fortunately, you can easily test your queries against a real database, as described below.
Functional Testing¶
If you need to actually execute a query, you will need to boot the kernel
to get a valid connection. In this case, you'll extend the KernelTestCase,
which makes all of this quite easy:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 | // tests/AppBundle/Repository/ProductRepositoryTest.php
namespace Tests\AppBundle\Repository;
use Symfony\Bundle\FrameworkBundle\Test\KernelTestCase;
class ProductRepositoryTest extends KernelTestCase
{
/**
* @var \Doctrine\ORM\EntityManager
*/
private $em;
/**
* {@inheritDoc}
*/
protected function setUp()
{
self::bootKernel();
$this->em = static::$kernel->getContainer()
->get('doctrine')
->getManager();
}
public function testSearchByCategoryName()
{
$products = $this->em
->getRepository('AppBundle:Product')
->searchByCategoryName('foo')
;
$this->assertCount(1, $products);
}
/**
* {@inheritDoc}
*/
protected function tearDown()
{
parent::tearDown();
$this->em->close();
$this->em = null; // avoid memory leaks
}
}
|
This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.