Problem/Motivation
In #3257127: Trigger a deprecation message when a deprecated module or theme is enabled we excluded deprecated modules from various tests. In most cases this didn't really lose any coverage, but ResolvedLibraryDefinitionsFilesMatchTest could be refactored to have two test methods - one against stable modules without @group legacy, and one testing only deprecated modules with it.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 3270499-3.patch | 3.42 KB | spokje |
Issue fork drupal-3270499
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:
- 3270499-add-a-deprecated
changes, plain diff MR !11884
Comments
Comment #3
spokjeComment #4
spokjeI _really_ don't understand why this still throws a deprecation notice, whilst in #3270323-12: ModuleConfigureRouteTest::testModuleConfigureRoutes fails for modules which have a configure route and are deprecated, where I do basically the same (load module in a test marked with
@group legacy) doesn't.Comment #8
quietone commentedReworked the patch a bit so there are two test methods.
Comment #9
smustgrave commentedAppears to be a good refactor to me, with the 2 separate functions now.
Comment #13
alexpottCommitted and pushed b8c04763730 to 11.x and cf5008b15b1 to 11.2.x and d9535798624 to 11.1.x. Thanks!
Backported to 11.1.x as this is a test-only change and makes it easier to backport things.
Comment #14
donquixote commentedIt appears this caused problems in 11.1.x.
See #3525090: [11.1] ResolvedLibraryDefinitionsFilesMatchTest is failing