@garvinhicking Would there be any way to have tests for this?

We need to verify that it does not change again in the future as our CI did not notice this error.

I will release version 5.2.1 today for this and PHPUnit 12 support. Thank you very much.

Thanks for the trust in advance. :) I'll see what I can do for some tests, I haven't yet checked this out, but should be possible. Give me a day or two.

@TavoNiievez I tried to get the tests up and running, according to the dockerized README in tests (https://github.com/Codeception/Codeception/blob/main/tests/README.md#dockerized-testing):

git clone ...
cd tests
docker-compose build
docker-compose up -d
docker-composer run --rm codecept run cli

which just yields:

Codeception PHP Testing Framework v5.2.1 https://stand-with-ukraine.pp.ua/
[Seed] 1553456819

In Assert.php line 2286:

  Result code was 1.

  Could not open input file: /repo/codecept

Seems that /repo/ is a mount to my cwd tests but there's no codecept directory and I wonder where it could stem from. What step could I be missing?

I assume that I would add tests with some dummy codeception.yaml files plus configured params: ... files with dummy files too, and then do assertions on non/failure variants, and do that in tests/cli/GlobalCommandOptionCest.php. However I need to get the tests to actually run, and my experience with codeception is just one as a consumer right now. If you have some docs to point me to to get this up and running, I'd be more than happy to contribute.