chore(deps): upgrade phpunit to 9.x

CONTRIBUTING.md

@@ -1,23 +1,23 @@
 # Contributing guide
 
-- [Contributing guide](#Contributing-guide)
-  - [Local development](#Local-development)
-    - [Environment](#Environment)
-      - [PHP](#PHP)
-      - [Docker](#Docker)
+- [Contributing guide](#contributing-guide)
+  - [Local development](#local-development)
+    - [Environment](#environment)
+      - [PHP](#php)
+      - [Docker](#docker)
       - [docker-compose](#docker-compose)
-  - [Testing](#Testing)
-    - [Composer](#Composer)
-      - [Code style quick fix command](#Code-style-quick-fix-command)
-      - [All-in-one command](#All-in-one-command)
-      - [Unit tests](#Unit-tests)
-      - [Feature tests](#Feature-tests)
-    - [Docker](#Docker-1)
-      - [Building images](#Building-images)
-      - [Running composer commands in docker](#Running-composer-commands-in-docker)
-      - [Generating code coverage](#Generating-code-coverage)
-  - [Creating a Pull Request](#Creating-a-Pull-Request)
-  - [Why docker](#Why-docker)
+  - [Testing](#testing)
+    - [Composer](#composer)
+      - [Code style quick fix command](#code-style-quick-fix-command)
+      - [All-in-one command](#all-in-one-command)
+      - [Unit tests](#unit-tests)
+      - [Feature tests](#feature-tests)
+    - [Docker](#docker-1)
+      - [Building images](#building-images)
+      - [Running composer commands in docker](#running-composer-commands-in-docker)
+      - [Generating code coverage](#generating-code-coverage)
+  - [Creating a Pull Request](#creating-a-pull-request)
+  - [Why docker](#why-docker)
 
 ## Local development
 
@@ -121,6 +121,13 @@ Or to build specific services use
 docker-compose build --pull composer
 ```
 
+*Info: When your docker installation support BuildKit (docker v18.09+) you can export bellow environment variables to archive faster builds*
+
+```sh
+export COMPOSE_DOCKER_CLI_BUILD="1"
+export DOCKER_BUILDKIT="1"
+```
+
 #### Running composer commands in docker
 
 You can run any composer command directly in docker container using bellow snippets:

Dockerfile

@@ -87,13 +87,13 @@ ENV COVERAGE="1" \
 COPY --chown=app:runner --from=composer-bin /usr/bin/composer /usr/local/bin/composer
 COPY --chown=app:runner --from=app-installer /usr/src/app ./
 
-FROM base as Cli
+FROM base as cli
 USER app:runner
 COPY --chown=app:runner --from=app-installer /usr/src/app ./
 ENTRYPOINT ["./tests/Fixtures/Symfony/app/console"]
 CMD ["swoole:server:run"]
 
-FROM Cli as Composer
+FROM cli as Composer
 ENV COMPOSER_ALLOW_SUPERUSER="1"
 COPY --chown=app:runner --from=composer-bin /usr/bin/composer /usr/local/bin/composer
 ENTRYPOINT ["composer"]

README.md

@@ -41,7 +41,7 @@ Symfony integration with [Swoole](https://www.swoole.co.uk/) to speed up your ap
     cd ./project
     ```
 
-3. Install bundle in your symfony application
+3. Install bundle in your Symfony application
 
     ```bash
     composer require k911/swoole-bundle
@@ -70,19 +70,19 @@ Symfony integration with [Swoole](https://www.swoole.co.uk/) to speed up your ap
 
 - Built-in API Server
 
-    Swoole Bundle API Server allows to manage Swoole HTTP Server in real time.
+    Swoole Bundle API Server allows managing Swoole HTTP Server in real-time.
 
     - Reload worker processes
     - Shutdown server
     - Access metrics and settings
 
 - Improved static files serving
 
-    Swoole HTTP Server provides a default static files handler, but it lacks supporting many `Content-Types`. In order to overcome this issue, there is (not yet configurable) Advanced Static Files Server. Static files serving is enabled by default in development environment. Static files directory defaults to `%kernel.project_dir%/public`.
+    Swoole HTTP Server provides a default static files handler, but it lacks supporting many `Content-Types`. To overcome this issue, there is (not yet configurable) Advanced Static Files Server. Static files serving remains enabled by default in the development environment. Static files directory defaults to `%kernel.project_dir%/public`.
 
 - Hot Module Reload (HMR) - for development
 
-    Since Swoole HTTP Server runs in Event Loop and do not flush memory between requests, to keep DX equal with normal servers, this bundle uses code replacement techinque, using `inotify` PHP Extension to allow contionus development. It is enabled by default (when extension is found), and requires no additional configuration. You can turn it off in bundle configuration.
+    Since Swoole HTTP Server runs in Event Loop and does not flush memory between requests, to keep DX equal with normal servers, this bundle uses code replacement technique, using `inotify` PHP Extension to allow continuous development. It is enabled by default (when the extension is found) and requires no additional configuration. You can turn it off in bundle configuration.
 
 - Symfony Messenger integration
 

composer.json

@@ -39,9 +39,9 @@
         "phpstan/phpstan-beberlei-assert": "^0.12.2",
         "phpstan/phpstan-doctrine": "^0.12.9",
         "phpstan/phpstan-phpunit": "^0.12.6",
-        "phpunit/php-code-coverage": "^7.0",
-        "phpunit/phpcov": "^6.0",
-        "phpunit/phpunit": ">=8.0.4,<8.4.2|>8.4.2",
+        "phpunit/php-code-coverage": "^8.0.1",
+        "phpunit/phpcov": "dev-master as 7.0.1",
+        "phpunit/phpunit": "^9.0.1",
         "swoole/ide-helper": "~4.4.7",
         "symfony/debug": "^4.3.1|^5.0",
         "symfony/framework-bundle": "^4.3.1|^5.0",