Problem/Motivation
There are two test modules that are not in the 'Testing' package.
$ git grep "package: test"
core/modules/jsonapi/tests/modules/jsonapi_response_validator/jsonapi_response_validator.info.yml:package: testing
core/modules/system/tests/modules/legacy_hook_test/legacy_hook_test.info.yml:package: test
Steps to reproduce
Proposed resolution
Change the package to 'Testing'
Remaining tasks
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
Issue fork drupal-3615122
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3615122-move-test-modules
changes, plain diff MR !16736
Comments
Comment #2
quietone commentedComment #6
kieran.cottComment #7
longwaveMaybe we could write a unit test that checks this to prevent regressions when we add new test modules.
Comment #8
kieran.cottGood idea - I've added a unit test that dynamically discovers non-hidden test modules beneath core test directories and verifies each discovered module declares
package: Testing.Comment #10
longwaveThanks for adding the test! I reworked the code a bit to use
ExtensionDiscoveryso the discovery mechanism is the same as other module discovery, but the principle is the same.Comment #11
smustgrave commentedSeems good to me
While this should be standard I know the options module doesn't follow this, never knew why.
Comment #13
catchCommitted/pushed to main, thanks!
Doesn't apply to 11.x, but not really sure we need a backport?