[TASK] Run functional tests in ddev (#259)

Co-authored-by: Łukasz Uznański <l.uznanski@macopedia.com>

.ddev/config.yaml

@@ -12,17 +12,20 @@ mariadb_version: "10.5"
 mysql_version: ""
 hooks:
   post-start:
-    - exec: composer install --no-progress
+  - exec: composer install --no-progress
 omit_containers: [dba, ddev-ssh-agent]
+webimage_extra_packages: [parallel]
 use_dns_when_possible: true
 composer_version: ""
-web_environment: []
-webimage_extra_packages: [parallel]
+web_environment:
+- typo3DatabaseName=typo3
+- typo3DatabaseHost=db
+- typo3DatabaseUsername=root
+- typo3DatabasePassword=root
 
-
-# This config.yaml was created with ddev version v1.17.2
-# webimage: drud/ddev-webserver:v1.17.2
-# dbimage: drud/ddev-dbserver-mariadb-10.3:v1.17.0
+# This config.yaml was created with ddev version v1.17.7
+# webimage: drud/ddev-webserver:v1.17.7
+# dbimage: drud/ddev-dbserver-mariadb-10.3:v1.17.7
 # dbaimage: phpmyadmin:5
 # However we do not recommend explicitly wiring these images into the
 # config.yaml as they may break future versions of ddev.
@@ -61,6 +64,11 @@ webimage_extra_packages: [parallel]
 # "ddev xdebug" to enable xdebug and "ddev xdebug off" to disable it work better,
 # as leaving xdebug enabled all the time is a big performance hit.
 
+# xhprof_enabled: false  # Set to true to enable xhprof and "ddev start" or "ddev restart"
+# Note that for most people the commands
+# "ddev xhprof" to enable xhprof and "ddev xhprof off" to disable it work better,
+# as leaving xhprof enabled all the time is a big performance hit.
+
 # webserver_type: nginx-fpm  # or apache-fpm
 
 # timezone: Europe/Berlin

README.md

@@ -129,7 +129,7 @@ a widely adopted tool in TYPO3 Community, [ddev](https://github.com/drud/ddev),
 ## Running Composer commands in the DDEV container
 
 If you use ddev, then you can use the provided command in root of your repository. You don't need to
-manually startup containers, you can run commands straight away, and project will automatically boot up.
+manually startup containers, you can run commands straight away, and project will automatically boot up. Please remember to keep ddev up to date.
 
 Example:
 
@@ -147,6 +147,14 @@ To run unit tests, type:
 composer ci:tests:unit
 ```
 
+### Functional tests
+
+To run functional tests, type:
+
+```bash
+composer ci:tests:functional
+```
+
 ## Running lints in CI
 ### GitHub
 For GitHub, we prepared two ways of running lints:
@@ -161,6 +169,7 @@ You can use prepared GitHub Actions. All of ready to use GitHub Actions are in
 An example workflow is defined in `ci.yml`
 ### GitLab
 For GitLab, please use the pipeline that is defined in `.gitlab-ci.yml`.
+
 ## Security
 
 Libraries and extensions do not need the security check as they should not have