docs(testing): update testing part using foundry instead of alice (#1757)

Author: Romaixn

distribution/testing.md

@@ -13,8 +13,8 @@ In this article you'll learn how to use:
 
 * [PHPUnit](https://phpunit.de), a testing framework to cover your classes with unit tests and to write
 API-oriented functional tests thanks to its API Platform and [Symfony](https://symfony.com/doc/current/testing.html) integrations.
-* [Alice](https://github.com/nelmio/alice) and [its Symfony
-integration](https://github.com/theofidry/AliceBundle#database-testing), an expressive fixtures generator to write data fixtures.
+* [DoctrineFixturesBundle](https://symfony.com/bundles/DoctrineFixturesBundle/current/index.html), a bundle to load data fixtures in the database.
+* [Foundry](https://github.com/zenstruck/foundry), an expressive fixtures generator to write data fixtures.
 
 ## Creating Data Fixtures
 
@@ -58,6 +58,8 @@ Improve the default values:
 
 ```php
 // src/Factory/ReviewFactory.php
+// ...
+use function Zenstruck\Foundry\lazy;
 
     // ...
 
@@ -156,6 +158,26 @@ The API Platform test client implements the interfaces of the [Symfony HttpClien
 
 If you don't use the distribution, run `composer require --dev symfony/test-pack symfony/http-client` to install them.
 
+Install [DAMADoctrineTestBundle](https://github.com/dmaicher/doctrine-test-bundle) to reset the database automatically before each test:
+
+```console
+docker compose exec php \
+    composer require --dev dama/doctrine-test-bundle
+```
+
+And activate it in the `phpunit.xml.dist` file:
+
+```xml
+<!-- api/phpunit.xml.dist -->
+<phpunit>
+    <!-- ... -->
+
+    <extensions>
+        <extension class="DAMA\DoctrineTestBundle\PHPUnit\PHPUnitExtension"/>
+    </extensions>
+</phpunit>
+```
+
 Optionally, you can install [JSON Schema for PHP](https://github.com/justinrainbow/json-schema) if you want to use the [JSON Schema](https://json-schema.org) test assertions provided by API Platform:
 
 ```console
@@ -175,15 +197,20 @@ namespace App\Tests;
 
 use ApiPlatform\Symfony\Bundle\Test\ApiTestCase;
 use App\Entity\Book;
-use Hautelook\AliceBundle\PhpUnit\RefreshDatabaseTrait;
+use App\Factory\BookFactory;
+use Zenstruck\Foundry\Test\Factories;
+use Zenstruck\Foundry\Test\ResetDatabase;
 
 class BooksTest extends ApiTestCase
 {
-    // This trait provided by AliceBundle will take care of refreshing the database content to a known state before each test
-    use RefreshDatabaseTrait;
+    // This trait provided by Foundry will take care of refreshing the database content to a known state before each test
+    use ResetDatabase, Factories;
 
     public function testGetCollection(): void
     {
+        // Create 100 books using our factory
+        BookFactory::createMany(100);
+    
         // The client implements Symfony HttpClient's `HttpClientInterface`, and the response `ResponseInterface`
         $response = static::createClient()->request('GET', '/books');
 
@@ -263,15 +290,22 @@ publicationDate: This value should not be null.',
 
     public function testUpdateBook(): void
     {
+        // Only create the book we need with a given ISBN
+        BookFactory::createOne(['isbn' => '9781344037075']);
+    
         $client = static::createClient();
         // findIriBy allows to retrieve the IRI of an item by searching for some of its properties.
-        // ISBN 9786644879585 has been generated by Alice when loading test fixtures.
-        // Because Alice use a seeded pseudo-random number generator, we're sure that this ISBN will always be generated.
         $iri = $this->findIriBy(Book::class, ['isbn' => '9781344037075']);
 
-        $client->request('PUT', $iri, ['json' => [
-            'title' => 'updated title',
-        ]]);
+        // Use the PATCH method here to do a partial update
+        $client->request('PATCH', $iri, [
+            'json' => [
+                'title' => 'updated title',
+            ],
+            'headers' => [
+                'Content-Type' => 'application/merge-patch+json',
+            ]           
+        ]);
 
         $this->assertResponseIsSuccessful();
         $this->assertJsonContains([
@@ -283,6 +317,9 @@ publicationDate: This value should not be null.',
 
     public function testDeleteBook(): void
     {
+        // Only create the book we need with a given ISBN
+        BookFactory::createOne(['isbn' => '9781344037075']);
+
         $client = static::createClient();
         $iri = $this->findIriBy(Book::class, ['isbn' => '9781344037075']);
 
@@ -294,22 +331,12 @@ publicationDate: This value should not be null.',
             static::getContainer()->get('doctrine')->getRepository(Book::class)->findOneBy(['isbn' => '9781344037075'])
         );
     }
-
-    public function testLogin(): void
-    {
-        $response = static::createClient()->request('POST', '/login', ['json' => [
-            'email' => '[email protected]',
-            'password' => 'admin',
-        ]]);
-        
-        $this->assertResponseIsSuccessful();
-    }
 }
 ```
 
-As you can see, the example uses the [trait `RefreshDatabaseTrait`](https://github.com/theofidry/AliceBundle#database-testing)
-from [AliceBundle](https://github.com/theofidry/AliceBundle) which will, at the beginning of each
-test, purge the database, load fixtures, begin a transaction, and, at the end of each test, roll back the
+As you can see, the example uses the [trait `ResetDatabase`](https://symfony.com/bundles/ZenstruckFoundryBundle/current/index.html#database-reset)
+from [Foundry](https://github.com/zenstruck/foundry) which will, at the beginning of each
+test, purge the database, begin a transaction, and, at the end of each test, roll back the
 transaction previously begun. Because of this, you can run your tests without worrying about fixtures.
 
 There is one caveat though: in some tests, it is necessary to perform multiple requests in one test, for example when creating a user via the API and checking that a subsequent login using the same password works. However, the client will by default reboot the kernel, which will reset the database. You can prevent this by adding `$client->disableReboot();` to such tests.