Drupal 11 support for ddev phpunit

[mscieszka]

I have installed Drupal 11.0-dev to investigate issues with the phpunit (next major) pipeline in https://gitlab.com/drupalspoons/devel/-/jobs/7146821758. Pipeline from gitlab templates invokes phpunit differently than ddev-drupal-contrib:

sudo -u www-data -E vendor/bin/phpunit  --bootstrap /builds/drupalspoons/devel/web/core/tests/bootstrap.php /builds/drupalspoons/devel/web/modules/custom/devel --log-junit /builds/drupalspoons/devel/junit.xml  

When I try to run phpunit in my local project using ddev phpunit, I get the following error:

The PHPUnit 10.5 documentation seems to indicate that there is no --printer flag.

In .ddev/commands/phpunit there is the following code:
phpunit --printer="\Drupal\Tests\Listeners\HtmlOutputPrinter" --bootstrap $PWD/$DDEV_DOCROOT/core/tests/bootstrap.php --testdox $DDEV_DOCROOT/modules/custom "$@"

I have noticed that HtmlOutputPrinter is present in Drupal 10.3, but has been moved/removed/modified in 11.x.

After some digging I have found Drupal\TestTools\Extension\HtmlLogging\HtmlOutputLogger that might be helpful.

However, simply removing --printer="\Drupal\TestTools\Extension\HtmlLogging\HtmlOutputLogger" part of the command so that only phpunit --bootstrap $PWD/$DDEV_DOCROOT/core/tests/bootstrap.php --testdox $DDEV_DOCROOT/modules/custom "$@" remains, allows phpunit to run properly (still, I am not sure if output is formatted/handled as expected):

[weitzman]

FYI We removed --testdox recently in #63.

We do want to keep the browser output so lets see how to fix this properly.

[weitzman]

I removed --printer in #70. I think the debug files are saved just by the fact that we set BROWSERTEST_OUTPUT_DIRECTORY. We can add back the links if we want. See https://www.drupal.org/project/drupal/issues/3452519