Document how to run api-platform/docker-compose-prod locally (#1014)

Author: teohhanhui

deployment/docker-compose.md

@@ -150,3 +150,11 @@ These steps should be performed on the production server.
     If you are using the (optional) Let's Encrypt integration:
 
         $ docker-compose -f docker-compose-prod/docker-compose.yml -f docker-compose-prod/docker-compose.letsencrypt.yml up -d
+
+##  Running the Docker Compose Setup for Production Locally
+
+Sometimes, you may need to run a production-like setup locally; for example, for [end-to-end testing](../distribution/testing.md#using-the-api-platform-distribution-for-end-to-end-testing)
+or to troubleshoot problems which can only be reproduced with a production setup (e.g. Varnish errors or cache misses).
+
+You may (re)use the same [Docker Compose setup for production](https://github.com/api-platform/docker-compose-prod) we
+have [installed above](#installing-the-docker-compose-setup-for-production).

distribution/testing.md

@@ -237,7 +237,7 @@ To do so, learn how to write unit tests with [PHPUnit](https://phpunit.de/index.
 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
-  [Behavior-Driven development](https://en.wikipedia.org/wiki/Behavior-driven_development) framework to write the API
+  [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
@@ -246,3 +246,15 @@ You may also be interested in these alternative testing tools (not included in t
   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);
 * [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
+
+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.
+
+Usually, this 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).