Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
note that this patch:
1) is work in progress
2) contains nothing but tests.
3) only enables modules, disabling them and uninstalling them.
4) depends on at least #516150: Add fallback for main content block rendering getting in.
5) exposes some broken stuff in HEAD
6) managed to get PHP errors from common.inc
7) should be future-proof when done.
Comment | File | Size | Author |
---|---|---|---|
testing_broken_drupal.patch | 7.1 KB | alexanderpas | |
Comments
Comment #1
sunProper description, please.
Comment #2
chx CreditAttribution: chx commentedWe already have tests for enabling and disabling modules please check/amend them as necessary instead of writing a new one thanks.
Comment #4
alexanderpas CreditAttribution: alexanderpas commented@chx
We never had tests that test what happens when all modules get enabled at the same time.
We also never had tests that disables all modules.
knowing this, and seeing the amount of breakage this patch revealed, this test is an good addition.
also, this test should be working perfectly (when finished) when a new core module get's added.
@sun
The tests provided by this patch tests what happens when all core modules get enabled at the same time, (our current tests only tests one or two modules at the same time), what happens when all core modules gets disabled at the same time (adhering to required-by (when properly coded.)) and what happens when all core modules providing uninstallation are uninstalled at the same time.
Comment #5
alexanderpas CreditAttribution: alexanderpas commented#607238: Permissions are assumed to be unique among modules, but uniqueness is not enforced needs to be fixed before i can reroll this one.
Comment #6
sun.core CreditAttribution: sun.core commentedTests don't qualify as critical.
Comment #7
longwaveTesting has moved on a long way, closing this as outdated.