Establish "core/tests/$type" as a canonical place for test extensions

Created on 18 August 2023, over 1 year ago
Updated 13 November 2023, about 1 year ago

Problem/Motivation

Currently there is no good place for test modules for core tests.
There are currently modules in core/tests/Drupal/Tests/Core/Extension/modules/, but this causes confusion with nested PSR-4 directories.

For now I want to use this for 📌 Add kernel tests for hook system Needs work and 📌 Add kernel tests for event system RTBC .

Steps to reproduce

n/a

Proposed resolution

Establish core/tests/$type as the canonical place:

  • core/tests/modules/ for modules.
  • core/tests/themes/ for themes.
  • core/tests/profiles/ for profiles?

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

📌 Task
Status

Needs work

Version

11.0 🔥

Component
Base 

Last updated about 16 hours ago

Created by

🇩🇪Germany donquixote

Live updates comments and jobs are added and updated live.
  • Needs subsystem maintainer review

    It is used to alert the maintainer(s) of a particular core subsystem that an issue significantly impacts their subsystem, and their signoff is needed (see the governance policy draft for more information). Also, if you use this tag, make sure the issue component is set to the correct subsystem. If an issue significantly impacts more than one subsystem, use needs framework manager review instead.

  • Needs change record

    A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.

Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024