Testing my plugin against Moodle 5.0 and PHP 8.4 I faced deprecation notices on the PHPUnit tests execution.
I can see from https://docs.phpunit.de/en/10.5/error-handling.html that we could pass (I would like) --display-deprecations --display-notices --display-warnings to the phpunit command, or the equivalent on the moodle-plugin-ci phpunit.
I think that when contributing to Moodle-related repositories, these options would be very welcome for both parts (either for the contributor and also the maintainer), who do not need to make a local installation or whatever to check what kind of notices they are. Maintainer could simply say something like "hey! look at the workflow XXX, there are some deprecations you should address. Thanks!"
Do you consider that this is something interesting for your workflows? Something like PHPUNIT_OPTIONS="--display-deprecations" or similar, and then use these options into the phpunit step.
Thanks for your work,
Jordi
Testing my plugin against Moodle 5.0 and PHP 8.4 I faced deprecation notices on the PHPUnit tests execution.
I can see from https://docs.phpunit.de/en/10.5/error-handling.html that we could pass (I would like)
--display-deprecations --display-notices --display-warningsto the phpunit command, or the equivalent on themoodle-plugin-ci phpunit.I think that when contributing to Moodle-related repositories, these options would be very welcome for both parts (either for the contributor and also the maintainer), who do not need to make a local installation or whatever to check what kind of notices they are. Maintainer could simply say something like "hey! look at the workflow XXX, there are some deprecations you should address. Thanks!"
Do you consider that this is something interesting for your workflows? Something like
PHPUNIT_OPTIONS="--display-deprecations"or similar, and then use these options into the phpunit step.Thanks for your work,
Jordi