PHPUnit notices or errors?

PHPUnit notices or errors?

by Renaat Debleu -
Number of replies: 0
Picture of Core developers Picture of Plugin developers

When Moodle runs 28879 PHPUnit tests on ci.moodle.org, you see 20 notices and 15429 deprecations.

When I run PHPUnit tests using the command:

vendor/bin/phpunit --display-deprecations --display-notices

the notices turn into errors and debugging warnings:

1) core\session\memcached_test::test_destroy
Error: Typed property core\session\memcached_test::$memcached must not be accessed before initialization
lib/tests/session/memcached_test.php:90

2) core\session\memcached_test::test_destroy_all
Error: Typed property core\session\memcached_test::$memcached must not be accessed before initialization
lib/tests/session/memcached_test.php:90

3) core_analytics\model_test::test_enable
Unexpected debugging() call detected.
Debugging: Prediction processor Python machine learning backend is not ready to be used. Model 130000 could not be cleared.
lib/phpunit/classes/advanced_testcase.php:88

...

Isn't it time to display notices and deprecations on the integration servers?

Average of ratings: -