Problem/Motivation

Drupal CMS currently uses raw phpunit to run tests in its gitlab pipeline.

This is due to run-tests.sh struggling with autoloading (I don't know the exact error).

Also I'm not sure whether run-tests.sh can discover Drupal CMS's recipe tests in the repository layout that it has, but we should make sure that works as well. This way, Drupal CMS and eventually other large composite recipes/site templates would be able to take advantage of the method ordering and concurrency optimisations that core + contrib modules already do.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Comments

catch created an issue. See original summary.

mondrake’s picture

mondrake
Location 🇮🇹
commented
Issue tags: +run-tests.sh
mondrake’s picture

mondrake
Location 🇮🇹
commented
Related issues: +#3538002: [backport] run-tests.sh - separate test allocation to bins into a WorkAllocator class

Contrib currently does not benefit of test methods ordering for concurrency optimization on run-test.sh, since it’s only implemented for test runs that use PHPUnit test suites for segmenting execution. Contrib using GitLab Templates use directory based filtering.

Please review #3538002: run-tests.sh - separate test allocation to bins into a WorkAllocator class that extends ordering to other filtering logics.

mondrake’s picture

mondrake
Location 🇮🇹
commented
Related issues: +#3549601: Allow --directory and @group to work together in run-tests.sh

also related

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.