Create a new component for the test runner

Open on Drupal.org →

Created on 28 August 2023, 10 months ago

Updated 6 February 2024, 4 months ago

Problem/Motivation

lib/Drupal/Core/Test contains a mixture of different things - some are for test classes, some for the SUT in functional tests, and some for the test runner.

From slack:

> I think lib/Drupal/Core/Test is stuff the runner needs. which isn’t a very good criteria, since the runner really should be its own component or at least somewhere other than inside core.

This issue is for creating a new component for the test runner. Classes from lib/Drupal/Core/Test should be moved to this new component.

Steps to reproduce

Proposed resolution

Identify which classes need to move to the new component. Possibly the following:

\Drupal\Core\Test\Exception\MissingGroupException
\Drupal\Core\Test\RunTests\TestFileParser
\Drupal\Core\Test\EnvironmentCleaner
\Drupal\Core\Test\EnvironmentCleanerInterface
\Drupal\Core\Test\JUnitConverter
\Drupal\Core\Test\PhpUnitTestRunner
\Drupal\Core\Test\SimpletestTestRunResultsStorage
\Drupal\Core\Test\TestDatabase
\Drupal\Core\Test\TestDiscovery
\Drupal\Core\Test\TestKernel
\Drupal\Core\Test\TestRunnerKernel
\Drupal\Core\Test\TestRun
\Drupal\Core\Test\TestRunResultsStorageInterface
\Drupal\Core\Test\TestStatus

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

📌 Task

Status

Active

Version

11.0 🔥

Component

Last updated about 1 hour ago

Maintained by
🇬🇧United Kingdom @alexpott
🇨🇭Switzerland @Berdir
🇩🇪Germany @dawehner
🇮🇹Italy @mondrake

Created by

🇬🇧United Kingdom joachim

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Comments & Activities

Issue created by @joachim
Comment 10 months ago →
🇺🇸United States Mile23 Seattle, WA
👍
Comment 10 months ago →
🇺🇸United States Mile23 Seattle, WA
Related but super-low priority: #2624926: Refactor run-tests.sh for Console component. →
Comment 4 months ago →
🇦🇺Australia mstrelan
Added a suggested list of classes to move to the new component.
Comment 4 months ago →
🇦🇺Australia mstrelan
If that list provided in the IS is correct then I'm not sure that this can be a component, since it has dependencies on classes from inside core, e.g. \Drupal\Core\Database\Database
Comment 4 months ago →
🇬🇧United Kingdom joachim
I assumed since the classes we're moving are currently in lib/Drupal/Core, the new component would also be in lib/Drupal/Core.

There isn't a word for 'thing that's inside lib/Drupal/Core', AFAIK 'component' is used for both lib/Drupal/Core and lib/Drupal/Component.
Comment 4 months ago →
🇦🇺Australia mstrelan
In that case what is meant by "at least somewhere other than inside core" in the slack thread?

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024