Adjust Core phpunit.xml to make it work for Contrib
Problem/Motivation
#3480767: browser_output is empty when testing with Drupal 11 and _phpunit_concurrent=0 changed the phpunit runner from executing with no phpunit.xml to using the core phpunit.xml.
This change causes a behavior change by specifying additional configuration.
One of the values is adding the Core directories as paths that should be included in code coverage analysis when they previously would not.
In several modules (S3FS, TFA, Vault, RabbitMq) code coverage is currently enabled with the intent that only the module paths should be included (both for increased test performanced/decreased time, and the fact the module tests are not intended to cover core). This has caused a code coverage reduction (and hours of lost developer time attempting to find the cause).
Steps to reproduce
Checkout https://git.drupalcode.org/project/vault/-/merge_requests/19
Run using the firecow runner against 1.6.3 and 1.6.4.
gitlab_templates: 1.6.3
phpunit > Code Coverage Report:
phpunit > 2024-11-09 16:26:48
phpunit >
phpunit > Summary:
phpunit > Classes: 6.67% (1/15)
phpunit > Methods: 53.09% (43/81)
phpunit > Lines: 80.15% (432/539)
gitlab_templates: 1.6.4
phpunit > Code Coverage Report:
phpunit > 2024-11-09 16:24:10
phpunit >
phpunit > Summary:
phpunit > Classes: 0.03% (1/3321)
phpunit > Methods: 0.24% (44/18454)
phpunit > Lines: 0.31% (434/141321)
Proposed resolution
Revert #3480767: browser_output is empty when testing with Drupal 11 and _phpunit_concurrent=0 (per API policy) and find alternative fix that does not depend upon adding phpunit.xml to the test script.
Consider adding phpunit.xml in v2 of GitLab Templates and at same time add a check for '--no-configuration' flag.