Codeception v5

[Naktibalda]

PHPUnit 10 will be released at the beginning of February and there is always a significant demand to support the latest PHPUnit.
On the other hand, if we implement that support in minor version, it may break tests for some of our users, because some functionality they rely on will be removed or changed. So it is a good reason to increment major version and release Codeception 5.0.

Please post what other changes you would like to see implemented on Codeception v5.

Here is what I'm going to do for Codeception v5:

• Merge the latest branch of phpunit-wrapper back to Codeception/Codeception
• Merge "Improved compatibility with PHPUnit 7+" changes made in codeception/codeception and phpunit-wrapper repos.
• Remove some old PHPUnit compatibility hacks
• Remove support for Symfony 3 (raise the lowest supported version to 4.4)
• Remove support for old versions of php-dotenv 2 and 3 (possibly 4 too).
• Remove support for codeception/stub v2
• Upgrade to the latest major versions of the following dependencies:
  • codeception/specify 0.* to 1.* Removed dependency instead because it wasn't used by tests
  • monolog/monolog 1.* to 2.* (used by ext/Logger.php) Removed dependency instead because Logger has no tests.
  • squizlabs/php_codesniffer 2.* to 3.* Removed because it wasn't part of CI and code style wasn't enforced. It can be readded latter.
• Delete deprecated code
  • Codeception\Util\Stub was deprecated in 2.3.8, 3 years ago
  • settings: bootstrap: setting was deprecated in 3.1.0 in August 2019
• Review all phpunit-wrapper code in src/PHPUnit/.
• Run tests of require-dev modules in Github Actions (this change will be backported to 4.1)
• Make codeception/stub compatible with PHPUnit 10.
• Update files in src/PHPUnit/NonFinal directory with the latest revision of their counterparts in PHPUnit (the only difference was that they have no final keyword, because some Codeception classes extend them).
• Make it work with PHPUnit 10 after final release.
• Check how much work it is to make with PHPUnit 9. Support it if it is simple (e.g. a few version or method_exists conditions).
• Repeat this process with PHPUnit 8.

It would be good to support PHP 7.2 in v5, then we can build phar files for PHP 7.2 with Codeception v5 and phar files for PHP 5.6 with Codeception v4.
If we keep building 2 phar files for Codeception v4 and build 1 or 2 new phar files for v5, some creative solution will be required to keep phar self-update functionality working for v4 PHP 7.2 files. Probably the latest version of that file will stay at https://codeception.com/codecept.phar , but Codeception 5 build will be at https://codeception.com/php73/codecept.phar

[ThomasLandauer]

Remove support for Symfony 3 (probably raise the lowest supported version to 4.4)

Symfony 3.4 is supported till November https://symfony.com/releases/3.4, so maybe it's too early to drop it?

[Naktibalda]

My intention is to support Codeception 4 for at least one year, so users of Symfony 3 can continue using it.

[samdark]

Some references:

• https://phpunit.de/supported-versions.html
• https://www.php.net/supported-versions.php

[Naktibalda]

I started working on it: #6067

[Naktibalda]

The latest version of TODO list is in my pull request.

[TavoNiievez]

maybe it's a good time to:

<?php

declare(strict_types=1); 

everywhere.

[Naktibalda]

100% is a high bar.

The only place I don't want to change method signatures in this release is interfaces and classes implemented or extended by modules.
It would be good to keep modules compatible with Codeception v4.

[TavoNiievez]

@Naktibalda Have you changed your mind about typing the interfaces?

I think that if we type all the interfaces that would be a good excuse to go from PHP 7.1 to PHP 7.3, since what would be intended would be that those new major versions of the modules are used with Codeception 5 that requires PHP 7.3

[Naktibalda]

I already agreed that changing interfaces is good idea in Codeception/lib-innerbrowser#39

[Naktibalda]

@DavertMik promissed to change directory structure in 5.0: #5727 (comment)

[DavertMik]

Ok, i will go with it!

[Naktibalda]

Advanced code coverage settings could be merged to 5.0: #5922
@SamMousa didn't want to support PHPUnit 8, so it is a one more reason to set lowest supported of PHPUnit to 9.0