|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +title: "Codeception 4.0 Released" |
| 4 | +date: 2019-12-18 01:03:50 |
| 5 | +--- |
| 6 | + |
| 7 | +We are finally here! |
| 8 | + |
| 9 | +Codeception 4.0 is released and this means a lot for us! |
| 10 | + |
| 11 | +After long months on splitting core into modules, publishing new packages and setting up build pipelines, we are proud to show you the result. |
| 12 | + |
| 13 | +As you know - Codeception 4 changes the way it is installed. From now on, Codeception package won't include any modules by default and you will need to install them manually. This can be a bit annoying at first but in the end, this will allow you to upgrade each package individually and not relying on the core. |
| 14 | + |
| 15 | +In Codeception 4 we also **added support for Symfony 5**, so if you plan to use the latest Symfony components - you need to upgrade today. |
| 16 | + |
| 17 | +## Upgrade to Codeception 4 |
| 18 | + |
| 19 | +To start upgrading to Codeception 4 bump a version in `composer.json` and run `composer update`. |
| 20 | + |
| 21 | +``` |
| 22 | +"codeception/codeception": "^4.0" |
| 23 | +``` |
| 24 | + |
| 25 | +To simplify the upgrading process **we introduced an upgrade script** which will go through your config file and scan for all included modules. Corresponding packages will be added to composer.json, so you could install all Codeception modules you need. |
| 26 | + |
| 27 | +Run upgrade script on current project: |
| 28 | + |
| 29 | +``` |
| 30 | +php vendor/bin/codecept init upgrade4 |
| 31 | +``` |
| 32 | + |
| 33 | +The script will upgrade your `composer.json` file and it is recommended to run `composer update` immediately, so new modules will be installed. |
| 34 | + |
| 35 | +If you use several Codeception configs for multiple bundles you will need to execute upgrade script for each of them: |
| 36 | + |
| 37 | +``` |
| 38 | +php vendor/bin/codecept init upgrade4 -c src/app/frontend/ |
| 39 | +``` |
| 40 | + |
| 41 | +Congratulations! An upgrade is done. Now you will be able to use each module individually. |
| 42 | + |
| 43 | +**Thanks to Gintautas Miselis @Naktibalda for splitting the core and adding Symfony 5 support** |
| 44 | + |
| 45 | +## Phar Distribution |
| 46 | + |
| 47 | +Codeception 4.0 will provide two phar files with selected modules included. One file will target PHP 7.2+ and include Symfony 4.4, PHPUnit 8 and newer versions of other libraries. Another file will target PHP 5.6 - 7.1 and include Symfony 3.4 and PHPUnit 5.7. |
| 48 | + |
| 49 | +Target audience of phar files is acceptance testers, so framework modules won't be included. |
| 50 | +Here is the full list of bundled modules: |
| 51 | + |
| 52 | +* Amqp |
| 53 | +* Apc |
| 54 | +* Asserts |
| 55 | +* Cli |
| 56 | +* Db |
| 57 | +* FileSystem |
| 58 | +* FTP |
| 59 | +* Memcache |
| 60 | +* Mongodb |
| 61 | +* PhpBrowser |
| 62 | +* Queue |
| 63 | +* Redis |
| 64 | +* Rest |
| 65 | +* Sequence |
| 66 | +* Soap |
| 67 | +* Webdriver |
| 68 | + |
| 69 | +Phar files will no longer be built on release of codeception/codeception, but on more ad-hoc basis either monthly or after important changes to core or some bundled module. |
| 70 | + |
| 71 | +## What's new in 4.0 |
| 72 | + |
| 73 | +Since 4.0 our [longread changelogs](https://codeception.com/changelog) are gone. So to track changes in modules you will need to go to corresponding repositories and read changelogs. For instance, here is [the changelog for Db module](https://github.com/Codeception/module-db/releases). |
| 74 | + |
| 75 | +However, we will still publish changelogs for core changes here. And one of the most interesting features coming to Codeception 4 is command stashing in interactive pause. |
| 76 | + |
| 77 | +Codeception 3.0 introduced interactive pause for better writing and debugging tests. By adding `$I->pause()` to your tests you could try all Codeception commands while a test will be interrupted. This helps for browser testing and framework testing, so you could try commands in action before leaving a test. |
| 78 | + |
| 79 | +In Codeception 4.0 this instrument was improved so you could automatically stash all successful commands: |
| 80 | + |
| 81 | + |
| 82 | + |
| 83 | +Use hotkeys to save successful commands into a file. So you no longer need to keep in mind which commands you need to take into your test. Just copy all successful commands and paste them into a test. |
| 84 | + |
| 85 | +*Stashing was brought to you by Poh Nean* |
| 86 | + |
| 87 | +--- |
| 88 | + |
| 89 | +Thank you for using Codeception, and thank you for staying with us these years. |
| 90 | +It is December 2019, so it means that **Codeception turns 8**. Through these years we reached 15Mln installations on Packagist, we are used in some well-known companies and we became a valuable part of PHP ecosystem. |
| 91 | + |
| 92 | + |
| 93 | +We accept congratulations [in Twitter](https://twitter.com/codeception) or [on OpenCollective](https://opencollective.com/codeception). If your business gets some value from Codeception it is ok to support its maintainers. Especially, today, when we have to maintain not one repository but 32! So, if possible, talk to your boss and ask for sponsoring Codeception. This means a lot to us, Codeception Team, and it will motivate us to work more on Codeception. |
| 94 | + |
| 95 | +We say "thank you" to all our current and previous sponsors: |
| 96 | + |
| 97 | +* Thanks to **[ThemeIsle](https://opencollective.com/themeisle)** for becoming our first regular financial contributor |
| 98 | +* Thanks to Sami Greenbury, Lars Moelleken, Dan Untenzu for investing their own money into open-source |
| 99 | +* Thanks to Rebilly and 2Amigos who fully supported the development since 2013 till 2016 |
| 100 | +* Thanks to Seravo for sponsoring Codeception 3.0 release. |
| 101 | + |
| 102 | +That's all. Upgrade to Codeception 4 and improve your testing! |
0 commit comments