Update for changes to System requirements

Cannot find a way out.

1) Cannot bump PHPUnit to 11 as core jobs do. PHPUnit 11 requires sebastian/diff 6, but apparently drupal/core-recommended has requirements that block both updates.

2) Trying to run tests by specifying --directory instead of --module does not work. Strange because tests for Image effects do work: https://git.drupalcode.org/project/image_effects/-/pipelines/508827

Going to bed now...

@mondrake should be credited wherever we end up fixing our Gitlab setup, when that happens (or in 📌 MissingGroupException: Missing group metadata with run-tests.sh in 11.2.0-dev Active )

Question: in this type of build, what is the path to the directories where test classes are defined? In relation if possible to Drupal's core /core subdirectory.

Asking because if it's missing from the list here (example for Javascript tests section of core's phpunit.xml.dist), we may want to try to add to the MR in 📌 Deprecate TestDiscovery test file scanning, use PHPUnit API instead Active .

    <testsuite name="functional-javascript">
      <directory>tests/Drupal/FunctionalJavascriptTests</directory>
      <directory>modules/**/tests/src/FunctionalJavascript</directory>
      <directory>recipes/*/tests/src/FunctionalJavascript</directory>
      <directory>profiles/**/tests/src/FunctionalJavascript</directory>
      <directory>themes/**/tests/src/FunctionalJavascript</directory>
      <directory>../modules/**/tests/src/FunctionalJavascript</directory>
      <directory>../profiles/**/tests/src/FunctionalJavascript</directory>
      <directory>../themes/**/tests/src/FunctionalJavascript</directory>
    </testsuite>

That seems extremely shippable, and definitely blocks a 2.1.0 release since that's the one with Drupal 11.2 compatibility.

Wünderbar! This is great.

Automatically closed - issue fixed for 2 weeks with no activity.