Adding upgrading instructions

Author: ThomasLandauer

_posts/2022-07-28-codeception-5.markdown

@@ -26,7 +26,7 @@ tests/
   Unit/
 ```
 
-All suite names will have their own namespace, as well as actor and helper classes:
+All suite names have their own namespace, as well as actor and helper classes:
 
 ```php
 <?php
@@ -44,7 +44,28 @@ class LoginCest
 }
 ```
 
-This new directory structure will be generated by running `codecept bootstrap`. The directory structure is set with a new default config, so the previous directory structure is still valid.
+This new directory structure will be generated by running `codecept bootstrap`.
+
+### Upgrading from Codeception 4
+
+Codeception 5 is compatible with the Codeception 4 directory structure. So if you don't want to change your file locations now, just keep your existing `codeception.yml`, and everything's fine.
+
+However, if you want to upgrade to the new Codeception 5 directory structure (recommended), here's the new default `codeception.yml`:
+
+```yaml
+namespace: Tests
+support_namespace: Support
+paths:
+    tests: tests
+    output: tests/_output
+    data: tests/Support/Data
+    support: tests/Support
+    envs: tests/_envs
+actor_suffix: Tester
+extensions:
+    enabled:
+        - Codeception\Extension\RunFailed
+```
 
 ## Attributes
 
@@ -103,6 +124,10 @@ Also new functions were added:
 * `codecept_pause()` - starts interactive pause anywhere in debug mode
 * `codecept_debug()` - prints a variable to console using Symfony VarDumper
 
+### Upgrading from Codeception 4
+
+Just remove `hoa/console` from your `composer.json`.
+
 ## Sharding
 
 The [Parallel Execution guide](/docs/ParallelExecution) has been rewritten and focused on a new feature: sharding. It is the simplest way to run slow tests (think of acceptance tests first) in parallel on multiple agents.