changeset 3644:062a09705d43

doc (contributing): fix `docker-compose-e2e.yml` spelling
author Goffi <goffi@goffi.org>
date Wed, 08 Sep 2021 11:15:24 +0200 (2021-09-08)
parents 30196b9a2b4c
children e65395e5f649
files doc/contribuing/testing.rst
diffstat 1 files changed, 3 insertions(+), 3 deletions(-) [+]
line wrap: on
line diff
--- a/doc/contribuing/testing.rst	Wed Sep 08 11:14:53 2021 +0200
+++ b/doc/contribuing/testing.rst	Wed Sep 08 11:15:24 2021 +0200
@@ -28,7 +28,7 @@
 ================
 
 End-to-end tests are located in ``tests/e2e``. They are launched in a well defined
-environment managed through Docker. The ``docker/docker-compose_e2e.yml`` is used to
+environment managed through Docker. The ``docker/docker-compose-e2e.yml`` is used to
 create the suitable containers.
 
 A script is available at ``tests/e2e/run_e2e.py`` to launch the tests. It will create the
@@ -68,7 +68,7 @@
   To log-in into the ``backend`` container, you can use the following command, from
   ``/docker`` directory::
 
-  $ docker-compose -f docker-compose_e2e.yml exec backend /bin/bash
+  $ docker-compose -f docker-compose-e2e.yml exec backend /bin/bash
 
   Then run a python console with given instructions
 
@@ -224,7 +224,7 @@
 …then to go into the ``backend`` container and work with the browser (to be run in ``docker``
 directory)…::
 
-  $ docker-compose -f docker-compose_e2e.yml exec backend /bin/bash
+  $ docker-compose -f docker-compose-e2e.yml exec backend /bin/bash
 
 …and, inside the container, you can now run ``python3`` and enter instruction prints at
 the end of the test session.