docs: modernize the testing tutorial (#1693)

Author: dunglas

distribution/testing.md

@@ -11,13 +11,11 @@ Let's learn how to use them!
 
 In this article you'll learn how to use:
 
-* [PHPUnit](https://phpunit.de/index.html), a testing framework to cover your classes with unit tests and to write
+* [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.
 
-Official [Symfony recipes](https://flex.symfony.com/) are provided for both tools.
-
 ## Creating Data Fixtures
 
 Before creating your functional tests, you will need a dataset to pre-populate your API and be able to test it.
@@ -69,17 +67,20 @@ The list of available generators as well as a cookbook explaining how to create
 
 ## Writing Functional Tests
 
-Now that you have some data fixtures for your API, you are ready to write functional tests with [PHPUnit](https://phpunit.de/index.html).
+Now that you have some data fixtures for your API, you are ready to write functional tests with [PHPUnit](https://phpunit.de).
+
+The API Platform test client implements the interfaces of the [Symfony HttpClient](https://symfony.com/doc/current/components/http_client.html). HttpClient is shipped with the API Platform distribution. The [Symfony test pack](https://github.com/symfony/test-pack/blob/main/composer.json), which includes PHPUnit as well as Symfony components useful for testing, is also included.
 
-Install the Symfony test pack (which includes PHPUnit and [PHPUnit Bridge](https://symfony.com/doc/current/components/phpunit_bridge.html)), [Symfony HttpClient](https://symfony.com/doc/current/components/http_client.html)
-(the API Platform test client is built on top of Symfony HttpClient, and allows to leverage all its features) and [JSON Schema for PHP](https://github.com/justinrainbow/json-schema) (used by API Platform to provide [JSON Schema](https://json-schema.org/) test assertions):
+If you don't use the distribution, run `composer require --dev symfony/test-pack symfony/http-client` to install them.
+
+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
 docker compose exec php \
-    composer require --dev symfony/test-pack symfony/http-client justinrainbow/json-schema
+    composer require --dev justinrainbow/json-schema
 ```
 
-Your API is ready to be functionally tested. Create your test classes under the `tests/` directory.
+Your API is now ready to be functionally tested. Create your test classes under the `tests/` directory.
 
 Here is an example of functional tests specifying the behavior of [the bookstore API you created in the tutorial](index.md):
 
@@ -245,31 +246,35 @@ Check out the [testing documentation](../core/testing.md) to discover the full r
 ## Writing Unit Tests
 
 In addition to integration tests written using the helpers provided by `ApiTestCase`, all the classes of your project should be covered by [unit tests](https://en.wikipedia.org/wiki/Unit_testing).
-To do so, learn how to write unit tests with [PHPUnit](https://phpunit.de/index.html) and [its Symfony/API Platform integration](https://symfony.com/doc/current/testing.html).
+To do so, learn how to write unit tests with [PHPUnit](https://phpunit.de/) and [its Symfony/API Platform integration](https://symfony.com/doc/current/testing.html).
+
+## Continuous Integration, Continuous Delivery and Continuous Deployment
+
+Running your test suite in your [CI/CD pipeline](https://en.wikipedia.org/wiki/Continuous_integration) is important to ensure good quality and delivery time.
+
+The API Platform distribution is [shipped with a GitHub Actions workflow](https://github.com/api-platform/api-platform/blob/main/.github/workflows/ci.yml) that builds the Docker images, does a [smoke test](https://en.wikipedia.org/wiki/Smoke_testing_(software)) to check that the application's entrypoint is accessible, and runs PHPUnit.
+
+The API Platform Demo [contains a CD worklow](https://github.com/api-platform/demo/tree/main/.github/workflows) that uses [the Helm chart provided with the distribution](../deployment/kubernetes.md) to deploy the app on a Kubernetes cluster.
 
 ## Additional and Alternative Testing Tools
 
 You may also be interested in these alternative testing tools (not included in the API Platform distribution):
 
-* [Behat](http://behat.org/en/latest/) and its [Behatch extension](https://github.com/Behatch/contexts), a
+* [Foundry](https://github.com/zenstruck/foundry), a modern fixtures library that will replace Alice as the recommended fixtures library soon;
+* [Hoppscotch](https://docs.hoppscotch.io/features/tests), create functional test for your API
+  Platform project using a nice UI, benefit from its Swagger integration and run tests in the CI using [the CLI tool](https://docs.hoppscotch.io/cli);
+* [Behat](http://behat.org), a
   [behavior-driven development (BDD)](https://en.wikipedia.org/wiki/Behavior-driven_development) framework to write the API
   specification as user stories and in natural language then execute these scenarios against the application to validate
   its behavior;
 * [Blackfire Player](https://blackfire.io/player), a nice DSL to crawl HTTP services, assert responses, and extract data
-  from HTML/XML/JSON responses ([see example in API Platform Demo](https://github.com/api-platform/demo/blob/master/test-api.bkf));
-* [Postman tests](https://www.getpostman.com/docs/writing_tests) (proprietary), create functional test for your API
-  Platform project using a nice UI, benefit from [the Swagger integration](https://www.getpostman.com/docs/importing_swagger)
-  and run tests in the CI using [newman](https://github.com/postmanlabs/newman);
+  from HTML/XML/JSON responses;
 * [PHP Matcher](https://github.com/coduo/php-matcher), the Swiss Army knife of JSON document testing.
 
-## Using the API Platform Distribution for End-to-end Testing
+## Using the API Platform Distribution for End-to-End Testing
 
 If you would like to verify that your stack (including services such as the DBMS, web server, [Varnish](https://varnish-cache.org/))
-works, you need [end-to-end (E2E) testing](https://wiki.c2.com/?EndToEndPrinciple).
-
-It is also useful to do a [smoke test](https://en.wikipedia.org/wiki/Smoke_testing_(software)) to check that your application
-is working; for example, that the application's entrypoint is accessible. This could be used as a quick test after each
-Docker build to ensure that the Docker images are not broken.
+works, you need [end-to-end (E2E) testing](https://wiki.c2.com/?EndToEndPrinciple). To do so, we recommend using [Playwright](https://playwright.dev) if you use have PWA/JavaScript-heavy app, or [Symfony Panther](https://github.com/symfony/panther) if you mostly use Twig.
 
-Usually, this should be done with a production-like setup. For your convenience, you may [run our Docker Compose setup
+Usually, E2E testing should be done with a production-like setup. For your convenience, you may [run our Docker Compose setup
 for production locally](../deployment/docker-compose.md#running-the-docker-compose-setup-for-production-locally).