- Issue created by @donquixote
- last update
over 1 year ago 30,047 pass - @donquixote opened merge request.
- Status changed to Needs review
over 1 year ago 2:49pm 18 August 2023 - 🇩🇪Germany donquixote
I think this needs some kind of test, but not sure yet how.
We can add a proof-of-concept module and have a test to discover it.
Will this be enough? Is it necessary? - 🇩🇪Germany donquixote
Instead of a dedicated test, we could use the two issues I mentioned as proof-of-concept.
If these work, we know that the change is ok. - Status changed to RTBC
over 1 year ago 1:38pm 21 August 2023 - 🇺🇸United States smustgrave
I love the idea! If committers agree think we should open a follow up to move the existing modules to the new directory.
- last update
over 1 year ago 30,056 pass - 🇩🇪Germany donquixote
move the existing modules to the new directory.
Just as a note:
Currently the modules incore/tests/Drupal/Tests/Core/Extension/modules/
, incore/tests/Drupal/Tests/Core/Database/fixtures/core/modules/
and incore/tests/fixtures/
are not found by ExtensionDiscovery.
They are used for unit tests where we have to manually add these paths.
Moving them to a place where they are discovered _could_ have side effects that we need to watch out for.
I don't see any name clashes with test modules in core/modules/**/tests/, so I guess it will be fine. - last update
about 1 year ago 30,056 pass - last update
about 1 year ago 30,058 pass - last update
about 1 year ago 30,060 pass - last update
about 1 year ago 30,063 pass - last update
about 1 year ago 30,130 pass - last update
about 1 year ago 30,135 pass - last update
about 1 year ago 30,136 pass - last update
about 1 year ago 30,136 pass - last update
about 1 year ago 30,146 pass 46:05 42:49 Running- last update
about 1 year ago 30,150 pass - last update
about 1 year ago 30,153 pass, 1 fail - last update
about 1 year ago 30,149 pass, 2 fail - last update
about 1 year ago 30,168 pass - last update
about 1 year ago 30,168 pass - last update
about 1 year ago 30,205 pass - last update
about 1 year ago 30,208 pass - last update
about 1 year ago 30,360 pass - last update
about 1 year ago 30,361 pass - last update
about 1 year ago 30,360 pass - last update
about 1 year ago 30,371 pass - last update
about 1 year ago 30,377 pass - last update
about 1 year ago 30,377 pass - last update
about 1 year ago 30,384 pass - last update
about 1 year ago 30,393 pass - last update
about 1 year ago 30,397 pass - last update
about 1 year ago 30,397 pass - last update
about 1 year ago 30,415 pass - last update
about 1 year ago 30,420 pass - last update
about 1 year ago Custom Commands Failed - last update
about 1 year ago Custom Commands Failed - last update
about 1 year ago Custom Commands Failed - last update
about 1 year ago Custom Commands Failed - last update
about 1 year ago Custom Commands Failed - last update
about 1 year ago Custom Commands Failed - last update
about 1 year ago Custom Commands Failed - last update
about 1 year ago Custom Commands Failed - last update
about 1 year ago Custom Commands Failed - last update
about 1 year ago Custom Commands Failed - 🇺🇸United States xjm
I think this addition should have either testing topic maintainer or FM review (tagged both, but really just one or the other would do). Thanks!
- last update
about 1 year ago Custom Commands Failed - last update
about 1 year ago Custom Commands Failed - Status changed to Needs work
about 1 year ago 1:46am 13 November 2023 - 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
This looks reasonable to me, and is consistent with how we store test modules for core modules.
I have one concern regarding the weight, specifically that we have core/modules at weight 0, ie explicitly the lowest in the priority. This is for example to allow a contrib version of a core module (e.g. CKEditor4, RDF) to take precedence over core when both exist (such as towards the end of Drupal 9).
Adding this new directory at weight 6 means it would take precedence over the other locations. I think instead it should probably be given weight -1 and added before the core directory. So that it gets the lowest precedence.
But in terms of the concept, I think this makes sense.
Is there an existing module in core/tests/Drupal/Tests/Core/Extension/modules/ we can move as part of this issue to provide implicit test coverage?
This will also need a change record and a followup to move any other existing modules.